My First Technical Job – T-SQL Tuesday #150
I’m late to the party on May’s T-SQL Tuesday, but thought it was an interesting enough topic to be worth a belated blog post. It’s about first technical jobs...
2022-06-05
36 reads
I’m late to the party on May’s T-SQL Tuesday, but thought it was an interesting enough topic to be worth a belated blog post. It’s about first technical jobs...
2022-06-05
36 reads
This month’s T-SQL Tuesday is about how we look at SQL Server upgrades, hosted by Steve Jones. My experience of SQL upgrades is that they tend to be largely...
2022-02-08
8 reads
Sometimes it’s good to look back and appreciate what we have and how far we’ve come. This applies to many things, but today I’m talking about the humble hard...
2022-02-18 (first published: 2022-02-06)
556 reads
I recently encountered a requirement to estimate the size of (a lot of) nonclustered indexes on some very large tables due to not having a test box to create...
2021-08-13 (first published: 2021-08-01)
448 reads
I recently encountered a requirement to estimate the size of (a lot of) nonclustered indexes on some very large tables due to not having a test box to create...
2021-08-01
11 reads
While testing a script that involved calculating index record size recently I was getting some confusing results depending on server version, and after some digging it appears there was...
2021-07-28
66 reads
While testing a script that involved calculating index record size recently I was getting some confusing results depending on server version, and after some digging it appears there was...
2021-07-28
7 reads
Hopefully not many people are still configuring SSIS instances on SQL 2012 or 2014 – especially HA instances – but if you are, this post is for you. If...
2021-05-28
113 reads
Hopefully not many people are still configuring SSIS instances on SQL 2012 or 2014 – especially HA instances – but if you are, this post is for you. If...
2021-05-28
8 reads
Blocking in SQL Server can be good – after all, it’s one of the ways consistency is guaranteed – we usually don’t want data written to by two processes...
2021-05-24 (first published: 2021-05-13)
715 reads
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
By Brian Kelley
If you don't have a plan, you'll accomplish it. That's not a good thing.
By Steve Jones
Today Redgate announced that we are partnering with Bregal Sagemount, a growth-focused private equity...
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