Hi Richard,

You can set up a WMI alert in SQL Agent to notify you when mirroring state changes, see the Database Mirroring State Change Events section here:

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

There's also a script...

Thanks, we have done.

It filled with streaming backup files as snapshot backups aren't currently being used (system db file in the wrong place), plus the user db starting growing much...

Thanks.

Probably create the indexes, it's really your call though.

A good indicator is if the user_seeks, unique_compiles, avg_user_impact, and avg_total_user_cost are high in the dmv.

Beware just blindly creating them though, especially...

Indianrock - I think you might be better off starting a new topic for this issue mate 🙂

Cheers, that makes sense, but are the sharepoint databases going to remain on the second box?

Same issue if they are?

Could you tell us which columns are the clustered indexes on for each table?

Any nonclustered indexes on the table? You'll almost certainly get scans without them.

Is Field4 on Table1...

Note you can't use resource governor on the reporting service itself, only connections to the database.

So report rendering/processing etc will be ungoverned.

It's also not instance aware so you might not...

Cheers, the issue was that the LUN filled, went offline, and took the SQL instance with it!

We've removed the dependency, I just wasn't sure if it was a NetApp recommended...

I'm no expert in this, but I think if you drop the key in the first query, then you won't be able to decrypt anything encrypted with it, so the...

Urgh, mirroring nomenclature.

I tend to use:

Primary & Secondary - Server and FailoverPartner respectively (or, Primary = the server you expect to be the 'live' one most of the time).

These titles...

Perry, this is happening on the primary server when it's acting as the mirror; all the databases are...

muthyala_51 (7/18/2014)

But i am seeing like thousands of thousands login failure for every sec, is this really expected...

Sorry, bad grammar on my part!

I mean that is the expected behaviour.

Expected behaviour, no?

The connection string specifies ServerName and FailoverPartner. So the app tries ServerName first, then FailoverPartner if unsuccessful.

The login errors you're seeing are the attempts of your app...

Nice Q, thanks. My logic on data type promotion was right, but my arithmetic was lacking 🙂