Blast Off
SQL Server 2008 launches today and there's are additional events all across the country coming up.
2008-02-27
68 reads
SQL Server 2008 launches today and there's are additional events all across the country coming up.
2008-02-27
68 reads
2008-02-25
20 reads
Do you know how to suggest improvements or features for SQL Server? Or report bugs? You use Connect, but it needs some work before it will really help the product.
2008-02-25
68 reads
This Friday Steve Jones asks about capital at work and does it affect the way you do business.
2008-02-22
36 reads
2008-02-21
172 reads
2008-02-20
87 reads
2008-02-19
54 reads
2008-02-18
73 reads
A perspective from Richard Collins on the creation of a government IT profession in the UK.
2008-02-18
63 reads
This year TechEd is across two weeks, with a different focus for each. Which one would you rather attend.
2008-02-15
35 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