2008-10-27
2,825 reads
2008-10-27
2,825 reads
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
2008-06-11
3,512 reads
2008-06-03
3,534 reads
If you have configured database mirroring in synchronous with or without automatic failover mode, you can switch to the mirror server instance and make it available to the clients while you perform hardware or software maintenance on the principal server instance. So let’s see how we can do this:
2008-03-27
2,029 reads
Understanding different types of failovers/Role Switching and How do they internally work in database mirroring.
2008-03-14
1,255 reads
If your database goes offline, you’re probably up a creek, right? If you’re using SQL Server 2005 with SP1, however, the database mirroring feature can prevent disaster.
2008-02-19
3,726 reads
By James Serra
(Shameless plug: The price of my book “Deciphering Data Architectures: Choosing Between a Modern...
By Steve Jones
I was working with a customer and discussing how to do error handling. This...
By DataOnWheels
The 14th annual Ability Summit is a global event that I attended a few...
Comments posted to this topic are about the item The Journey to Change
Comments posted to this topic are about the item Check Azure SQL DB Space...
Comments posted to this topic are about the item The Cloned Database Size
I have a small test sandbox database on an instance with default master, model, msdb, and tempdb settings. The database has these files:I now run this command:
DBCC CLONEDATABASE(sandbox, sandbox_clone); GOWhen I examine the database file properties, what do they show? See possible answers