2,560
Two Thousand Five Hundred Sixty. Seems like such a random and unassuming number, however, I can say this was the...
2012-10-23
1,432 reads
Two Thousand Five Hundred Sixty. Seems like such a random and unassuming number, however, I can say this was the...
2012-10-23
1,432 reads
When I was considering submitting some sessions to SQL Saturday 149 in Minnesota I thought I would have a difficult...
2012-09-22
796 reads
In my article published yesterday on using Powershell for SQL Durations (Working with SQL Agent Durations), I proposed using a...
2012-08-24
1,605 reads
That is what I wanted to name the new training series that we developed at my employer, Perpetual Technologies (PTI.net)....
2012-08-09
1,009 reads
This last weekend, I had the pleasure of being invited down to Louisville, KY to speak at SQL Saturday #122....
2012-07-24
985 reads
It has been a great couple of months for both me and for Perpetual Technologies (my employer). PTI has been...
2012-07-09
861 reads
In my previous post, I shared some of the issues I had when attempting to get Add-Member to work with...
2012-07-05
1,492 reads
Over the past few weeks, I’ve been working with SMO to implement some maintenance routines across my clients. Because of...
2012-07-04 (first published: 2012-06-28)
3,941 reads
I wish I could say that this was a simple task, but as I dove into SMO and some of...
2012-06-19
2,721 reads
I’ve been working a lot lately with SMO and the differences between the various versions between SQL 2005, 2008, and...
2012-06-06
17,435 reads
By Brian Kelley
Tech conferences aren't just for networking and learning how to address a problem you're...
By DataOnWheels
When I created the website on WordPress, I was expecting all the features I...
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
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