I've always rebooted after any MS service pack (SQL or Windows) whether they say to or not. It's served me well ... call it a 'best practice' ...

A little late, but the term describing the initial SQL statement is 'almost' a 'cartesian join' ...

Everything but the file move is handled. You can add an additional Job step to perform this task to accomplish this.

Just one question ... "Why not use SQL Maintenance Plans ?" ...

52 Gb is not that large. based on all of the discussion the most efficient method seems to be:

1) backup the transaction log --> of course I'd also do a...

I do not believe that it is the EM at fault. It's the OS. You're probably a victem of disk fragmentation.

Also, you will have to stop/restart the SQL Server service.

here's a start .from BOL ...

xp_logininfo [[@acctname =] 'account_name'] [,[@option =] 'all' | 'members']

    [,[@privelege =] variable_name OUTPUT]

In actuality, the users requesting the change have all the knowledge needed, after all it is a business process and business decision driving this. What they are probably lacking are...

Without sufficient power 'failover' will not help unfortunately.

There's also one more 'esoteric' limitation when using views ... the concatenated columns of the views cannot exceed the usable page size (approx. 8092 bytes out of an 8192 -...

3 things. First to make the mapping 'go away' in SQL Server you will have to stop and restart SQL Server. Second, if you use this again, I'd also add /PERSISTENT:NO. Finally...

IMHO 5 minutes UPS time is not enough 'battery time' for a SQL server. This lack of time for a graceful shutdown is probably the root cause of your corruption....

MOM --> Microsoft Operations Management is the tool that we use. It provides lots (repeat lots) of monitoring. Here's the main link below (plan on spending a hour or two...

how about:

exec xp_cmdshell 'DIR g:\cnd_reports\JmailAirCND.exe'

and

exec xp_cmdshell 'DIR \\server_name\share_name\cnd_reports\JmailAirCND.exe'