SQLServerCentral Editorial

Planning for tomorrow, today - database migrations

I have been speaking to people about database migrations to the cloud a lot over the last few weeks. One thing that has jumped out at me is that we seem to focus on the process of moving data being the migration rather than one step in a larger process. Many people neglect the discovery […]

You rated this post out of 5. Change rating

2025-09-20

89 reads

Blogs

Managing subscribers, creating newsletters

By

When I created the website on WordPress, I was expecting all the features I...

Finding the Last Last Name in SQL: #SQLNewBlogger

By

I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...

SQL Server Reliability: Clearing the Fuzzy Thinking

By

The terminology around reliability is a mess If you’ve ever said, “We’re covered, it’s...

Read the latest Blogs

Forums

Email change does not work

By rjkoala1

I changed my email address in Edit Profile page, but it has no effect...

The case for "Understanding our business" training

By David.Poole

Comments posted to this topic are about the item The case for "Understanding our...

Specifying the Collation

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Specifying the Collation

Visit the forum

Question of the Day

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