SQL Server 2005 is out and everyone is moving to test and deploy it. However many people are still managing SQL Server 2000 instances. New author Boris Baliner brings us a few tricks to find that information you are used to from Enterprise Manager.
2007-10-02 (first published: 2006-03-16)
35,483 reads
As everyone moves to SQL Server 2005 from SQL Server 2000, there are quite a few pieces of information that have moved and may give you trouble finding. Boris Balinger brings us a followup to his first look at some of those changes with a quick article on how you can get the free space in your database files.
2006-06-06
9,346 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...
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
Comments posted to this topic are about the item SQL Server 2025 has arrived!
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