anyone seen this before? It looks specifically to be the SP:Completed event that causes the delays. I suspect it's to do with the encrypted procedures, but 2005 worked...

yes. We still achieved more consistent results with setting maxdop.

weeks of testing demonstrated that MAXDOP 4 was most performant for our workload

looks specifically to be sp:Completed that's causing the problems. Any ideas?

I can't imagine it would be too difficult to add an additional parameter to accept "destination directory", and use that with the MOVE option of restore database command. If...

my 2 cents...

Estimated and actual rows are significantly different all over the place. I'd re-run an update statistics with full scan.

Estimated IO costs seem significantly higher for TempDB. ...

http://blogs.technet.com/b/rob/archive/2011/11/23/enabling-kerberos-authentication-for-reporting-services.aspx

My opinion would be to grow the existing file to what you would expect it to be in a 9 - 12 months time. 12GB is small by today's...

the default database is master.

This account is a domain admin. When we were on 2005, although it had permissions explicitly granted at the database/object level, it was a member...

hi,

Already tried that. It shows the database for the failed login attempt as 'master'. I'm hoping that that's still there!

Cheers, Andrew

sp_validatelogins doesn't return anything either

how does that answer my question?

Hi,

The CAP is called MIRRORSERVER. I can connect to MIRRORSERVER\INSTANCE1 via SSMS, but when I run: select auth_scheme from sys.dm_exec_connections where session_id = @@spid, it comes back NTLM. ...

thanks for the reply. It's sorted now. It looks like a fault with the VM the instance sits on. Cold booted the thing and it started working...

Turns out that something's wrong with our mirror server. I mirrored elsewhere and it works fine.

Basically, I am testing mirroring between SQL Server Client Access Points in 2 Windows...