T-SQL Tuesday #84: Growing New Speakers
This month's #tsql2sday is being hosted by Andy Yun (b|t) and is about helping new speakers.
I have only been speaking...
2016-11-08
416 reads
This month's #tsql2sday is being hosted by Andy Yun (b|t) and is about helping new speakers.
I have only been speaking...
2016-11-08
416 reads
This month's #tsql2sday is being hosted by Andy Yun (b|t) and is about helping new speakers.
I have only been speaking...
2016-11-08
214 reads
Got back from Summit on Saturday and I’m still totally in the moment. I came back with so many new...
2016-11-03
420 reads
Got back from Summit on Saturday and I’m still totally in the moment. I came back with so many new...
2016-11-03
201 reads
I think the title is fairly descriptive so let me put a little context around it for you. In my...
2016-10-25
763 reads
I think the title is fairly descriptive so let me put a little context around it for you. In my...
2016-10-25
288 reads
Question: Who owns your availability groups?
The person who creates the AG becomes the owner by default. Did you know that...
2016-10-20
16,779 reads
Question: Who owns your availability groups?
The person who creates the AG becomes the owner by default. Did you know that...
2016-10-20
281 reads
#TSQL2SDAY is a monthly blog party hosted by a different blogger each month. This blog party was started by Adam...
2016-10-11
385 reads
#TSQL2SDAY is a monthly blog party hosted by a different blogger each month. This blog party was started by Adam...
2016-10-11
199 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