Re-teaming is Good: Here’s Why
Note: This post is based on an editorial I originally published over at SQL Server Central Years ago, I worked on a fabulous team of eight database administrators We...
2020-03-13
17 reads
Altering an indexed view in SQL Server drops all indexes
I learned an interesting thing about ALTER VIEW behavior in SQL Server when applied to indexed views. This is covered in the product documentation, but it’s not something I...
2020-03-02
64 reads
Come work with me! Be a Sales Engineer for Redgate
Redgate is growing, and we have some fresh, new open positions around the world which would be a great fit for SQL Server developers or DBAs who would like...
2020-02-21
10 reads
I can do better; we can do better; let’s do better
In the past week or so, the Microsoft Data Platform community has begun having a discussion about inclusivity, both on Twitter and across community blog posts. This conversation began...
2020-02-13
9 reads
Protect Your Prod Databases in Azure DevOps / TFS: Three Control Points
When implementing any kind of automation for database deployments, it’s important to implement safeguards for your production environment. This is needed even in the best conditions when team members...
2020-02-05
17 reads
High Availability options for SQL Server 2008 in an Azure VM – a #sqlhelp story
I asked a question on Twitter yesterday: And check out the magic of the sqlhelp hash tag, I got loads of answers! So many that I’m actually selecting a...
2020-02-01
17 reads
Do It Live! A First Look at Redgate’s Hybrid Model for SQL Source Control and SQL Change Automation (video)
In this 70 minute livestream recording, I kick the tires of a fresh new Azure DevOps demo environment showing Redgate’s Hybrid Model for SQL Source Control and SQL Change...
2020-01-25
7 reads
Controlling who commits code to a given database schema in Git with Azure DevOps
One of most the fun things about working as an Advocate at Redgate is getting to help clients determine their preferred workflow for database DevOps. Teams often have unique...
2020-01-18
18 reads
Re-Inventing Humanity
Wishing you all a very happy, prosperous and peaceful new year 2020! May new year make us Human who cares for all the living being and for our mother...
2020-01-11
27 reads
Re-Inventing Humanity
Wishing you all a very happy, prosperous and peaceful new year 2020! May new year make us Human who cares for all the living being and for our mother...
2020-01-11
9 reads
Blogs
Post-quantum key exchange – Insurance policy for your packets
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Plan your 2026
By Brian Kelley
If you don't have a plan, you'll accomplish it. That's not a good thing.
Another Change
By Steve Jones
Today Redgate announced that we are partnering with Bregal Sagemount, a growth-focused private equity...
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