2018-01-29
60 reads
2018-01-29
60 reads
Kathi Kellenberger wonders what's keeping your business from upgrading.
2017-12-25
56 reads
When I began using LAST_VALUE, the results were not what I expected at all. Read on to learn the secret!
2016-06-03 (first published: 2015-04-14)
26,403 reads
2015-04-27
1,836 reads
2015-04-15
1,936 reads
2015-04-03
1,887 reads
I have several speaking events coming up, and I would love to see you there!
First of all, I'll be...
2012-07-11
1,041 reads
One of my favorite features of SQL Server Management Studio (SSMS) is the ability to run a script on multiple...
2012-03-02
2,573 reads
I drove the over 250 miles from my home in Edwardsville, IL, to attend the SQL Server 87 in Louisville,...
2011-11-02
1,315 reads
Once again I am back at home recovering from another PASS Summit. This year the attendance has exceeded all expectations...
2011-10-16
1,390 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...
Unlock the full potential of spreadsheets with our “Advanced Excel Mastery” course tailored for...
Prepare your team for the upcoming compliance shift with our “2025 Form 1099 Reporting...
Comments posted to this topic are about the item The case for "Understanding our...
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