2011-07-26 (first published: 2009-06-24)
8,780 reads
2011-07-26 (first published: 2009-06-24)
8,780 reads
2011-07-19 (first published: 2009-06-17)
9,670 reads
2011-07-12 (first published: 2009-06-03)
8,708 reads
2011-07-07 (first published: 2009-05-27)
8,646 reads
2011-06-30 (first published: 2009-05-13)
7,303 reads
2011-06-28 (first published: 2009-05-06)
7,730 reads
Transportation Management is an information technology problem in more ways than one.
2011-06-23 (first published: 2009-04-29)
7,202 reads
The pros and cons of having computing power close at hand.
2011-06-16 (first published: 2009-04-15)
8,532 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