With SQL Server 2012 Microsoft introduced the AlwaysOn Availability Group feature, and since then many changes and improvements have been made. This article is an update to another article, and will cover the prerequisites and steps for installing AlwaysOn in your SQL Server 2019 environment. Prerequisites Before implementing your AlwaysOn Availability Group (AG), make sure […]
2025-12-24 (first published: 2025-11-25)
658 reads
Is your SQL database log file too big? Maybe it is. But maybe it’s not. When log files keep growing and appear to be too big some might suggest switching to Simple recovery, shrinking the log file, and switching back to Full recovery. While this will work to shrink the file and free up disk […]
2022-02-16
30,888 reads
Keep column headers visible while scrolling down the page of SSRS reports.
2021-03-12 (first published: 2019-01-07)
8,573 reads
With SQL Server 2012 Microsoft introduced the AlwaysOn Availability Group feature, and since then many changes and improvements have been made. This article is an update to another article, and will cover the prerequisites and steps for installing AlwaysOn in your SQL Server 2019 environment. Prerequisites Before implementing your AlwaysOn Availability Group (AG), make sure […]
2020-12-07
151,854 reads
In part 2 of this article, learn how you can move incremental changes in a SQL Server table using Azure Data Factory.
2020-01-21
2,623 reads
Learn how to get started uploading data from a SQL Server to Azure Blob Storage.
2019-12-30
4,176 reads
2019-03-29 (first published: 2017-12-04)
5,774 reads
Whoever creates an AlwaysOn group is, by default, the owner of the endpoint. This is generally not a problem…unless that person leaves the company and you need to delete the login.
2018-10-25
15,478 reads
2017-07-04 (first published: 2015-12-14)
10,776 reads
2016-12-05
12,198 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