anishninan

Principal data architect with over 15 years of experience in Enterprise data warehousing, Machine Learning and AI. He helps customers including Fortune 500 companies define and execute their data strategy. He leads modern data estate projects using technologies such as Databricks, MLFlow, Azure Synapse, and SAP. He has over 6 successful data transformation projects under his belt and has led teams of up to 15 people. Currently at Hitachi he manages multiple critical customer engagements and is the SME on Databricks and Spark.

All authors

All authors

Blogs

Tech Conferences and Expanding Your View

By

Tech conferences aren't just for networking and learning how to address a problem you're...

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...

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