2020-11-10
669 reads
2020-11-10
669 reads
2019-06-14
1,548 reads
2019-05-14
665 reads
2019-03-21
749 reads
2019-02-27 (first published: 2019-02-20)
930 reads
This script features as we can through the CTE Top10FilesWithLargerDiskConsumption the top ten data files that are showing greater consumption of hard drive related data-reading activities.
2019-01-15 (first published: 2019-01-08)
1,050 reads
This script is intended to demonstrate how we can create a stored procedure for the user responsible for backing up user databases in a default storage location.
2018-07-10 (first published: 2018-07-05)
506 reads
2018-06-22
941 reads
Este bloco de código tem o objetivo de demonstrar como podemos inserir um quantidade de linhas de registro de dados aleatórios de uma tabela no Microsoft SQL Server.
2018-06-14 (first published: 2018-06-12)
1,420 reads
2018-05-22
838 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