Comparing Stored Procedures, Part 6
Sixth in a series of scripts demonstrating a quantitative comparison between the text of two stored procedures
2009-04-15 (first published: 2009-02-26)
1,401 reads
Sixth in a series of scripts demonstrating a quantitative comparison between the text of two stored procedures
2009-04-15 (first published: 2009-02-26)
1,401 reads
2009-04-06
4,527 reads
Fifth in a series of scripts demonstrating a quantitative comparison between the text of two stored procedures
2009-04-03 (first published: 2009-02-23)
1,405 reads
2009-02-11
3,909 reads
Reformats the text output of queries to trim trailing blanks in wide varchar columns for easy copy-and-paste.
2008-03-10 (first published: 2008-01-09)
2,928 reads
2008-03-06
5,020 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