Useful, thank you. I'd be interested in reading the possible follow up article you mentioned.

Useful script - thank you. It worked on most of my SQL2000/5/8/8R2s. However no data was returned on some of our SQL2005 clusters, I *guess* because those SQLs lacked permission...

I had a bad experience of Double Take some years back where I was asked to sort out a mess created by a systems guy (I'm a DBA) who had...

The fix was to add the IP of the SQL Server to a 'Hub Relay Service'. I don't know exactly where that sits (between SQL and Exchange or the Exchange...

Thanks for replying - if we get a fix, I'll post it here

I'm getting the same error too - did you find a solution?

This sounds like a good idea, certainly worth a try. Focusing on how products work (i.e. no marketing hype) should be useful.

I have worked from home in the UK (more systems DBA than applications) since 1999. It wasn't seen as a big deal as my work had become remote even when I was office...

Excellent, thank you!

Microsoft should hang their heads in shame and make this information EASILY AVAILABLE themselves!

It would also helpful if @@VERSION returned a unique software level. We became...

My list:

Steve Earle / El Corazon

Tom Petty / Anthology

The Beatles / Revolver

Gothic Voices / Hildegard Von Bingen - A Feather on the Breath of God

Rimsky-Korsakov / Scheherazade

Trouble is, if...

Yes the limitations are as you describe (we only do migrations of logins when transferring applications to a new instance) so I haven't looked at just transferring passwords.

I'd check whether Microsoft...

In Enterprise Manager check Server Properties | Security Level.  Perhaps your Audit Level is now 'All'?

That shouldn't change with a SP4 apply though. We've done dozens of SP4 applies...

Great article! We do something similar and also take account of server roles by querying syslogins and generating the syntax for sp_addsrvrolemember. Probably not an issue for most people.

I've occaisonally seen this and in each case it was due to tables in TEMPDB being locked by an application. I can't remember which ones but I used sp_lock to find...

I had the same error recently. Diagnostic messages were written to the maintenance plan report but not to the maintenance plan history. As you say "no logs were created" I guess...