2025-11-10
989 reads
2025-11-10
989 reads
2025-11-07
1,179 reads
2025-11-03
1,256 reads
This article shows how you can find which objects in your database might not be valid after schema changes.
2025-10-06
8,968 reads
2025-09-24
332 reads
2025-09-17
1,673 reads
2025-09-15
1,556 reads
2025-09-08
1,549 reads
We have some requirements that we meet a particular setting or value, but often we have guidelines and recommendations. Do you know the difference?
2025-09-05
77 reads
2025-09-05
1,541 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