2005-09-16
2,191 reads
2005-09-16
2,191 reads
2005-09-06
2,091 reads
I guess it might be because I have been so busy for the last two months with the book, but this...
2005-09-05
1,233 reads
2005-09-01
1,944 reads
The images on the TV news this morning were surreal. Hundereds of people dead, missing, homeless because of Katrina and...
2005-08-31
1,270 reads
I was just reading Andy Leonard's blog about being a new author and thought, hey, I need a blog, too!
I'm...
2005-08-29
1,323 reads
2005-08-23
2,151 reads
2005-08-18
1,886 reads
2005-08-10
1,972 reads
2005-08-04
2,097 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...
Hi everyone, I’m working with some old SSIS 2005 packages, and I’m trying to...
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...
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