2001-06-14
5,611 reads
2001-06-14
5,611 reads
2001-05-25
3,996 reads
By default, all NT administrators of the domain that your SQL Server is installed in, have SA rights in every database. This presents interesting challenge for DBAs, political and technical. Does your NT administrator group need SA rights to every database? The answer is no.
2001-05-25
4,068 reads
This article by Andy Warren provides an introduction to some of the fixed database roles and things to consider when using them.
2001-05-17
4,710 reads
Poorly managed SQL Server Security can not only leave your SQL Server vulnerable, but also leave your NT Server and network open to attacks.
2001-05-14
6,533 reads
This article by Andy Warren discusses both how to use the Public Role and how using Public may cause you more problems than it's worth. Great examples!
2001-05-10
18,542 reads
Using the sa account in development is just plain dumb. Here are some reasons why!
2001-05-08
6,804 reads
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
By Steve Jones
If you aren’t watching the Ignite keynotes today, then you might have missed the...
Short version You want to get this running as fast as possible. Do these...
I changed my email address in Edit Profile page, but it has no effect...
Comments posted to this topic are about the item The case for "Understanding our...
Comments posted to this topic are about the item Specifying the Collation
I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:
DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'
SELECT p.PersonType,
p.Title,
p.LastName,
c.CustomerID,
c.AccountNumber
FROM Person.Person AS p
INNER JOIN Sales.Customer AS c
ON c.PersonID = p.BusinessEntityID
COLLATE @c
Will this solve my problem? See possible answers