pound for pound, i have found it quicker to detach copy then re attach databases rather than backup and restore. Also dont forget the microsoft scripts to export your logins...

how many servers\databases are we talking?

how many characters is the servername currently?

is the SQL server a member server or stand alone server

could it be that someone has configured an application\web site to use the SA account? either way assign an obscure password to the account and then disable it. Use the...

set the recovery model to "bulk logged" during the purge and change back to simple after you have finished deleting data

you would be wise to furnish sql server with more memory rather than CPU. High CPU count will raise the software costs too 😉

for SQL2000 try this, it returns any objects not owned by sys or dbo just change it to look for your login (instead of excluding). To catch all DB's wrap...

exactly, BTW also forgot to mention that sa login is also disabled on our sql servers.

even under virtualisation 64bit isnt necessarily the defacto platform

if you plan on using perfom there are a set of key counters to look at, what do you plan to use?

assuming you have the arrays available 😀

humbleDBA (6/18/2008)

---

Colin,

I don't wholy disagree with you on the 64-bit vs 32-bit. In fact in most cases, and for DB servers that have large DBs and require performance then 64-bit...

just for reference and to help others with similar problems what was it you did? 😉

what monitoring tool(s) are you using?

our databases all get set to SA ownership and SA has a secure password.