2014-06-30
3 reads
2014-06-30
3 reads
2014-06-12
4 reads
2014-06-10
1 reads
2014-01-08
6 reads
2014-01-03
2 reads
2 years ago I posted “16 papers and original articles on Big Data” It’s now time to review and...
2013-06-01
11 reads
SQL Server 2012 brings a new feature called Indirect Checkpoint. You can read more about it here: http://msdn.microsoft.com/en-us/library/ms189573.aspx. With Indirect Checkpoint, you get smaller and too many I/Os Checkpoint...
2013-03-19
13 reads
The Big Data revolution will be more important than the PC or the Internet. While there were many...
2013-03-04
7 reads
2012-10-13
5 reads
2012-10-05
3 reads
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...
By Steve Jones
Last week I asked you to write about SQL Server 2025 and what things...
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
Comments posted to this topic are about the item SQL Server 2025 has arrived!
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