January 15, 2010 at 10:09 am
I have a mirrored database across a WAN, I have a witness (which is located in the same location as the Mirror server) that fails over automatically to the mirror server and so far it has been working fine. Currently, the database is 500MB large, but in the near future is going to be at least 60GB and I was wondering if there are any considerations or best practices that I have to review in order to keep the mirror working smoothly.
I was told that for the mirror it is convenient to have the SQL Browser service up and running, is that true?
Also, is there a way to establish a threshold in order to fail over (not to send alerts), the reason I'm asking is because sometimes the WAN has small 'hiccups' making the witness server to fail over unnecessarily.
Principal Database Server
OS: Windows 2008 Datacenter x64
SQL version: SQL Server 2005 x64 standard
Mirror and Winess servers:
OS: Windows 2003 Enterprise x64
SQL version: SQL Server 2005 x64 standard
January 15, 2010 at 4:01 pm
Also, is there a way to establish a threshold in order to fail over (not to send alerts), the reason I'm asking is because sometimes the WAN has small 'hiccups' making the witness server to fail over unnecessarily.
You can query sys.database_mirroring to find the connection timeout. The default is 10 seconds.
SELECT d.name, dm.mirroring_connection_timeout
FROM sys.database_mirroring dm
JOIN sys.databases d
ON dm.database_id = d.database_id
You can change the timeout value by using the following:
ALTER DATABASE <DBNAME> SET PARTNER TIMEOUT <SECONDS>
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply