Using undocumented DBCC WRITEPAGE to instigate SQL Server database corruption
In this tip look at the undocumented command DBCC WRITEPAGE to corrupt a SQL Server database and then use the command to undo the corruption.
2018-10-03
2,545 reads
In this tip look at the undocumented command DBCC WRITEPAGE to corrupt a SQL Server database and then use the command to undo the corruption.
2018-10-03
2,545 reads
2018-08-31
759 reads
2018-08-24
976 reads
2017-06-12
1,068 reads
2017-06-08
1,030 reads
2017-02-27
940 reads
2017-02-10
1,112 reads
2016-11-08
1,048 reads
2016-07-20
1,238 reads
2016-05-25
1,370 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