When a failover occurs, you actually restarting the SQL Server Instance on your cluster, so you're losing connection with the primary

As a result, your secondary DB will get a state...

Why can't you have automatic failover?

If it's synchronous you have the option "automatic failover"

See http://technet.microsoft.com/en-us/library/hh213151.aspx

Hi,

Can you be more specific on "AlwaysOn Availability Group created between SQLCluster & Node C"

Which commit mode did you use? Synchronous or Asynchronous?

And if you used Synchronous, did you activate...

Hi,

Did you actually find a solution for this problem?

I have the same issue.

DBCC CHECKDB is failing with the same error on msdb and master but not on model db.

All data...

Looks like it is SCCM 2012 installation that is adding 2 trace flags onto the SQL Server during installation...

http://blog.andernetwork.com/2011/08/21/sccm-2012-beta-2-installation-error-failed-to-write-string-t8295-to-registry-on-sql-server/

Still, what is it used for 🙂 ?

Regards

Pieter

Hi,

Did you manage to fix your problem because I have the same issue on my cluster...

Regards

Problem is when setting up the log shipping on the primary.

No secondary is involved yet.

Thanks for the info, but that doesn't explain why I don't have the backup compression option in the log shipping wizard of the Management Studio, however, I'm using the 2008...

Hi,

I have the same problem.

Did you already found a solution?

Regards

Pieter

Hi,

Probably your database is case-sensitive.

Try sp_MSforeachtable instead of sp_msForEachTable

So, only MS in capital letters.

Pieter