2025-09-01
1,659 reads
2025-09-01
1,659 reads
Learn about delayed durability in SQL Server and how it might help you with a heavily loaded server.
2025-08-29
8,284 reads
2025-08-29
532 reads
2025-08-22
382 reads
This is the first in a series of articles meant to provide practical solutions to common issues. In this post, we’ll talk about one of the most pervasive error messages out there:
2025-08-15
2025-07-18
5,820 reads
SQL Server has several functions to assist with meta data about the server, databases, indexes, and more. In this tip, we will look at how to get index information for indexes in a database using the INDEXPROPERTY function.
2025-06-27
There are multiple reasons for no full backup: corrupted backups, taking too much time to restore, etc. In this post, I want to show an alternative for these cases, an ace up one’s sleeve, that you can use to recover data.
2025-06-23
2025-05-28
347 reads
2025-05-19
549 reads
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
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...
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