A whole lot .Sometimes this things come up and since it is a database the DBA automatically has to take charge.

Have to learn about d base ..

Thanks again

Though that was not your question, Changing the snapshot isolation level too would alleviate blocking and there will be no need to write code to trap deadlocks

Create a new device..

Go to Server Objects

Right click on backup devices

New backup device

give the device a name

\\enter path name for new device

Then run a backup...

I will propose updating/ stats after the loads

Drop and recreate the device let us know if the issue persists

Verify that the seperate parts are working before putting them together

This is similar to an error I was having when log shipping was set .

That was taken care of though when I replaced local with the actual...

Update stats nightly on the temp tables and see what happens

I will use such a tool too if there is a good one out there

Checkout the datediff function

Cannot say for sure if that is the best option but that worked well for me

My opinion would be to say if you do not want some one to see anything in your db do not create the account in the first place .

On a personal note I do not.The once a night backups of the system DBs seem more than enough in my experience

backup log file shrink log and do a backup your restore should work just

Hard to tell exactly why you are having the errors but I can tell you backups and restores are for the most part very dependable in Mssql

If you are...