Thanks John for the response. These are system databases that aren't matched to the server collation...so the only thing I can think of is that master, msdb and model...

Awesome, i'll give it a try. Thanks!

Yes, completely right. I don't think it could be used to give a guaranteed minimum latency though if needed.

You could use log shipping to introduce a restore latency (in addition to the 'natural' latency of Log Shipping) for the Secondary DBs if you don't want it to be...

Are there any long running transactions? Also, when you manually back up the Log, is that with the DB still in the AG?

Superb, thanks Perry. Seems obvious now you've said that.

Cheers

Rod

We get the same issue when VMs are created from a template, I just use the below (which just uses sp_addserver and sp_dropserver as recommended above) to check and reset...

Very good point, The failover partner makes much more sense when witnesses are being used. We tend not to have auto failover due to our network 'setup'.

Rod

'Out of the box' its a manual process, if you have server names in the connect string for your app pointing at serverA then it will need to be manually...

Sorry, forgot to include how to use it

http://msdn.microsoft.com/en-us/library/df40c888-691c-4962-a420-78a57852364d(v=sql.100).aspx

Basically...something like..

setup.exe /ACTION=INSTALL /CONFIGURATIONFILE= {......} etc.

Hi, the easiest way to get you started I think is to use the Configuration File generated by SQL 2008+. If you go through the motions of an install,...

I would add baseline comparisons (OS & SQL) to the above as well, allows you to see quite quickly if something has changed from the norm.

Rod

Hi, the script below will look through the current default trace log for tables Altered/Created/Deleted. Just run it under the context of the DB in question AND enter your...

Fantastic script above! Thanks. Also, if you're using SQL 2008 R2 SP1 upwards, check out trace flag 2371 to see if its of any use.

Cheers

I've had a similar issue for 2 different situations in the past.

1) The base oracle client had been installed, but the server not rebooted post install. (SQL+ was...