Implementing SQL Server Failover Clustering in Azure virtual machines differs in several aspects from its on-premises implementations. These differences reflect some of the unique characteristics of the storage and network infrastructure services in the Microsoft cloud environment. In this article, Marcin Policht looks at the networking aspects of clustered deployments of SQL Server 2016 in Azure.
2017-10-11
2,735 reads
In this article, I’m going to talk an issue that I found when joining replica or database on secondary replica to availability group.
2020-01-31 (first published: 2017-04-17)
33,552 reads
In this article, I will show a procedure to isolate the replication traffic from the public network.
2017-04-10
10,496 reads
In this article, I will show you a procedure to combine SQL Server AlwaysOn with logshipping and to make log-shipping to work even in case of failovers between availability replicas in primary site.
2017-04-03
26,449 reads
2017-03-17
957 reads
In this edition of Office Hours, Brent, Erik, and Richie discuss AlwaysOn Availability Groups, execution plans, speeding up log shipping, applying wrong service packs, their favourite high availability solutions, and more.
2017-02-14
3,764 reads
2017-01-30
885 reads
A “multi-subnet” environment is defined when the OS cluster used as the backbone for AlwaysOn has server nodes that are located in multiple/different subnets. Deploying SQL Server AlwaysOn Availability Groups requires a Windows Server Failover Clustering (WSFC) cluster and each availability replica of a given availability group must reside on a different node of the same WSFC cluster. This post from Manvendra Singh will help you in configuring an HA and DR solution for SQL Server AlwaysOn in multi-subnet networks.
2017-01-13
3,309 reads
2017-01-02
896 reads
2016-12-16
926 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