Parsing T-SQL – The easy way
UPDATE 2012-09-12 : For my latest adventures with TSQL Parsers please see this post
Every once in a while, I hit an issue...
2012-03-13
11,073 reads
Dave Ballantyne
SQLMidlands & SQLLunch
Many thanks to all those that turned out to see my presentation on Thursday (16th of Feb) of “Cursors are...
2012-02-18
755 reads
[BUG] Inserts to tables with an index view can fail
Unfortunately some of the more troubling bugs can be very hard to reproduce succinctly. Here is one that has been...
2012-01-06
1,369 reads
Book review - SQL Server Secret Diary (Know the unknown secrets of SQL Server)
Like a lot of people within the SQL community, I can never read enough on the subject. Books, whitepapers, academic...
2011-12-31
2,315 reads
Extended Events - inaccurate_cardinality_estimate
Extended events have been a bit of a personal “Elephant in the room” for me. I know they are there...
2011-12-06
2,699 reads
MythBusting–“Table variables have no statistics”
Ok, as myths go, its a pretty weak one. In fact, it is true, this whitepaper explicitly states that. But...
2011-12-02
3,075 reads
Execution plan warnings–The final chapter
In my previous posts (here and here), I showed examples of some of the execution plan warnings that have been...
2011-11-29
1,848 reads
Blogging from 37,000ft
Im currently on my way to Sql Rally nordic and looking forward to a few days of full on SQL...
2011-11-06
625 reads
Execution plan warnings–All that glitters is not gold
In a previous post, I showed you the new execution plan warnings related to implicit and explicit warnings. Pretty much...
2011-11-06
839 reads
More Denali Execution Plan Warning Goodies
In my last blog, I showed how the execution plan in denali has been enhanced by 2 new warnings ,conversion...
2011-10-19
784 reads
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