Database Mirroring is Back in Azure SQL Database
Database Mirroring comes back to SQL, at least to Azure SQL Database with Fabric as the destination. Read a few of Steve's thoughts on this feature.
2024-03-30
498 reads
Database Mirroring comes back to SQL, at least to Azure SQL Database with Fabric as the destination. Read a few of Steve's thoughts on this feature.
2024-03-30
498 reads
In this article we look at a PowerShell script that can quickly retrieve information about all databases from all servers that are configured to use database mirroring.
2021-07-19
2017-06-26
858 reads
Server principal 'xx\yy' has granted one or more permission(s). Revoke the permission(s) before dropping the server principal. (Microsoft SQL Server, Error: 15173). If you are gett
2016-10-03 (first published: 2016-09-16)
3,158 reads
SQL Server Database Mirroring offers two methods for exchanging data: synchronously and asynchronously. Sometimes there may be a need to switch between modes for an existing mirror and in this tip we will look at how this can be done.
2015-08-03
3,376 reads
2015-07-15
1,409 reads
In this article, I describe some steps a DBA can take to check for mirroring on SQL Server, give a status of the mirroring state and some options for resolving any problems with the transaction log that might be caused by Database Mirroring.
2014-11-06
9,922 reads
2011-10-13
2,103 reads
2011-09-21
2,029 reads
2011-09-09
2,171 reads
By Steve Jones
I have been experimenting with MCP servers in a few ways, including the Redgate...
By Zikato
I deployed a schema change to 30 servers using multi-server query and deploy-at-low-priority. Small...
Fabric deployment pipelines look like they solve CI/CD for Fabric content, especially for people...
Comments posted to this topic are about the item A Challenge of Our Knowledge
Comments posted to this topic are about the item The memory toll of VARCHAR(MAX)...
Comments posted to this topic are about the item Transaction Log Truncation
In SQL Server 2025, where can I find information about items that prevent or delay the transaction log truncation?
See possible answers