Database Mirroring

External Article

Database Mirroring adjusting the automatic failover time

  • Article

One of the configuration options for Database Mirroring is the High Availability mode. With this option three servers are put in place the principal, mirror and witness servers. This is the only option that allows for automatic failover. One of the things that I have noticed is that when there are periodic network issues a failover occurs even though there are no issues with the Principal server. Are there any options to delay the failover?

2008-10-29

3,626 reads

External Article

Database Mirroring Automating Failover for Multiple Databases

  • Article

Database Mirroring was released with SQL Server 2005 and is becoming a popular choice for a failover solution. One of the big issues with Database Mirroring is that the failover is tied to one database, so if there is a database failure the mirrored server takes over for this one database, but all other databases remain functional on the primary server.

2008-09-08

4,007 reads

Blogs

T-SQL Tuesday #183 Roundup

By

I hosted this month’s T-SQL Tuesday party with my invitation asking about tracking permissions....

A Little Brainstorming with an AI

By

I was asked to do some a little thinking and brainstorming recently. Rather than...

The Mysterious Empty Table

By

It seems like no matter how long you work with a system beyond a...

Read the latest Blogs

Forums

how do you manage new columns in a tabular table

By stan

Hi we run 2019 ssas std.  Yesterday i imported my tabular project to vs...

Why I get null instead I should get 0

By hilme70

Code for mssql 2008 DECLARE @CompanyID TINYINT DECLARE @MemNo decimal DECLARE @MemberFrom Integer DECLARE...

bypass a non existing server

By mtz676

I have an execute task(has server list from a table) pointing to foraeachloop foreachloop...

Visit the forum

Question of the Day

Mixed Backups

I have a complex database with a few filegroups and files. Can I run a backup command like this? (assume file/filegroup names are valid).

BACKUP DATABASE [complex]
    FILE = N'thirdone'
 ,  FILE = N'thirdtwo'
 ,  FILEGROUP = N'second' 
 TO  DISK = N'C:\Program Files\Microsoft SQL Server\MSSQL16.SQL2022\MSSQL\Backup\complex.bak' 
 WITH NOFORMAT, NOINIT,  NAME = N'complex-Full Database Backup', SKIP, NOREWIND, NOUNLOAD,  STATS = 10
GO

See possible answers