If you are consolidating on a single instance of SQL Server, your only option is going to be scripting out the jobs and rebuilding on the new server.

Why would you want to do this?

There is a public role available - it does not have any permissions by default. You could add permissions to this role, but...

Litespeed comes with their own xp procedure to delete litespeed based backup files. Look in the documentation for Litespeed and it will show you how to script it out...

Add to the list:

Any query hints? If so, is it required and the documentation in place explaining why?

If you are migrating off of this system, why do you care? Once you have moved to the new system wouldn't you just retire the existing system and delete...

I agree with Jason...

Next items:

Are all objects schema qualified?

Are aliases defined and used?

Are there any functions being used in the where clause that would prevent index usage?

Are there any functions...

Why do you want to return the space to the OS? Your database is going to grow - so why not keep the space for the future growth of...

Yeah - I was afraid of that. And, no - I don't have any other suggestions - sorry.

Not sure this will work for your case, but you can lookup SOUNDEX and see if that gets you anywhere. Documentation here: http://msdn.microsoft.com/en-us/library/aa259235(SQL.80).aspx

I wasn't clear on whether or not the problem is with your log file - or your data file. If it is your log file, how often are you...

You are welcome - and thanks for the feedback, it is appreciated.

Are you trying to backup across the network? Is SQL Server running under a domain user account that has the necessary rights to the folder being backed up to?

Instead of using db_datareader, and then trying to remove all other access - it would be better to create your own role and add the specific rights you want to...

Error 33 is telling you that the file is locked by another process. One of the reasons for that could be a compressed volume. Another possibility is the...

You should start getting in the habit of terminating your SQL statements...