2012-01-18
9 reads
2012-01-18
9 reads
2011-08-24
10 reads
What are the most influential papers in the world of Big Data? Let me suggest:...
2011-05-30
7 reads
2011-05-02
4 reads
2011-02-02
8 reads
2011-01-05
7 reads
I searched the internet for “connect and forget”. Wonderbox.net offer is described as a...
2010-10-10
5 reads
10 years ago IT professionals considered database technology “mature” and analysts were preparing to...
2010-09-13
10 reads
“The information age is an idea that the current era will be characterized by the ability of...
2010-08-22
3 reads
“Content is king” is the golden rule of the SEO. The semantic web is all about data. Any web...
2010-06-25
10 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