Sql-server – Database Mirroring of SQL server

mirroringsql serversql-server-2005sql-server-2008

I have two databases that are mirrored to another server using database mirroring.

The mirror server has to be down for some reason for few days.

Now, the production server is having principal databases in (PRINCIPAL/DISCONNECTED) State.

Clients can access those databases.

Questions

So what happens when they keep on adding data to these databases??
Will the data get committed or waits till the mirror comes up?

Best Answer

Your .LDF log is growing, as it cannot be truncated because the mirror is unavailable. Eventually you'll run out of space unless you either break the mirroring or bring the mirror back online.

Related Solutions

Sql-server – Database Mirroring with TDE

Found a website with a comment on it.

I added the code to just after where I restore the key and cert

--Mumbojumbo to get mirroring to work
OPEN MASTER KEY DECRYPTION BY PASSWORD = '1Password'
ALTER MASTER KEY ADD ENCRYPTION BY SERVICE MASTER KEY
GO

It works like a charm, it makes a little sense that I had to encrypt the master key that I restored with the service master key of the new server. I guess.

shrug

Sql-server – Resuming Replication w/ Database Mirroring when Principle is unavailable

Trace flag 1448 was the answer...

DBCC TRACEON (1448, -1) on Server B immediately sent the record to the subscriber. No restart necessary.

Best Answer

Related Solutions

Sql-server – Database Mirroring with TDE

Sql-server – Resuming Replication w/ Database Mirroring when Principle is unavailable

Related Question