Analyzing Tempdb Spills and Usage Across Recursive Queries
This article examines how tempdb is affected by recursive queries, using a few different methods.
2025-05-23
2,091 reads
tempdb
2024-04-24
451 reads
2024-04-10
452 reads
2021-02-11
783 reads
SQL Server TempDB Tutorial
In this article we cover many different questions about the SQL Server TempDB database to give a better understanding of what is and what it is used for.
2020-07-27
2020-06-18
844 reads
2020-06-11
850 reads
2020-05-12
673 reads
2020-04-28
747 reads
Memory-Optimized TempDB Metadata in SQL Server 2019
In this article we look at a new feature in SQL Server 2019 that can help improve TempDB performance.
2019-12-19
Blogs
Flyway Tips: AI Deployment Script Descriptions
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
A New Word: Fawtle
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
Post-quantum key exchange – Insurance policy for your packets
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Forums
Where Your Value Separates You from Others
Comments posted to this topic are about the item Where Your Value Separates You...
Fixing the Error
Comments posted to this topic are about the item Fixing the Error
T-SQL in SQL Server 2025: Encoding Functions
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Question of the Day
Fixing the Error
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