Should I check tempdb for corruption?
You all know that checking our databases for corruption regularly is a must. But what about tempdb? Do you need...
2015-03-02
4,575 reads
You all know that checking our databases for corruption regularly is a must. But what about tempdb? Do you need...
2015-03-02
4,575 reads
We’re being told over and over that “throwing hardware at the problem” is not the correct solution for performance problems...
2015-02-24 (first published: 2015-02-12)
8,146 reads
Next week, on Saturday 28, make sure you don’t miss SQLSaturday Pordenone!
Pordenone is the place where the Italian adventure with SQLSaturday...
2015-02-19
643 reads
Some weeks ago I blogged about the discouraging signals coming from Connect and my post started a discussion that didn’t...
2015-02-02
549 reads
As you probably know, SQL Server allows only one default instance per server. The reason is not actually something special to...
2015-01-29
51,050 reads
A couple of years ago I blogged about a bug on the Data Collector that I couldn’t resolve but with an...
2015-01-12 (first published: 2015-01-07)
5,295 reads
Today when I checked my mailbox I found an amazing surprise: I joined the ranks of the Most Valuable Professionals...
2015-01-01
418 reads
Monitoring blocking and deadlocking hasn’t always been easy. Sometimes, the tools available in SQL Server are not as friendly as...
2014-12-12
1,836 reads
Does anybody need another good reason to avoid setting AUTO_CLOSE on a database? Looks like I found one.
Some days ago, all of...
2014-11-13
317 reads
Some weeks ago I had to wipe my machine and reinstall everything from scratch, SQL Server included.
For some reason that I...
2014-09-25
953 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