Search results for query: *

One way you could objectively analyze the impact of the export is to look at the length of time that it takes the job step to complete.

THe PERMS command in the resource kit lists an option to take control of a file.

Try the userdump utility from the resource kit.

I think what you want to do is the following: 1) Start - Run 2) Enter cmd - hit enter - this brings you to a command prompt. From there you can do all the typing for at commands. 3) to see the list of currently scheduled jobs, just type in at

There is a winsdmp.exe utility in the nt resource kit Bill L'Hotta

check to see if you have permissions on the share as well as on the files. If that isn't the problem, try to log on as the user yourself at the server, then on a remote workstation and see if you can duplicate the problem. Bill L'Hotta

Also make sure that the E drive is not compressed.

Just because you close the connection at the client doesn't mean that the server closes the connection. There is a timeout for each client connected to the database. Worst case, you can stop/start sql server service and you will be able to drop the database. I don't remember the timeout...

I had similar experiences using Veritas Netbackup product. Make sure your account is set up as system administrator under SQL. It may need to be in machine admins as well. If those steps fail, make sure you have explicit read/write permissions to each database. Good Luck