What happens when you cancel or kill a resumable index creation?
SQL Server 2019 adds resumable online index creation, and it’s pretty spiffy according to Brent.
2019-04-11
SQL Server 2019 adds resumable online index creation, and it’s pretty spiffy according to Brent.
2019-04-11
When you index a nullable field, are the rows with nulls stored in the index? It’s easy enough to find out by creating a table with a nullable field, and then creating an index on it.
2019-03-29
2019-03-28
395 reads
Michael J. Swart posted an interesting question: he had a large table with 7.5 billion rows and 5 indexes. When he deleted 10 million rows, he noticed that the indexes were getting larger, not smaller.
2019-03-22
2,752 reads
2018-11-09
817 reads
Tara explains when index DMVs gets reset by telling a story from her dark past.
2018-11-09
3,197 reads
When you're not sure, start by aiming for 5 or less indexes per table, with 5 or less fields each.
2018-11-02
4,276 reads
2018-10-29 (first published: 2018-10-19)
1,430 reads
2018-08-30
827 reads
2018-08-23
859 reads
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Comments posted to this topic are about the item Where Your Value Separates You...
Comments posted to this topic are about the item Fixing the Error
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:
SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error? See possible answers