Trying to kill the process yes you should try that first but it will most likely complain because it is a system process.

I would agree. I have found however some of the Idera tools have had some issues when interacting with a Clustered name instance of SQL server Enterprise addition. Never figured...

not that I have found worth looking in to.

This can also happen if you are trying to do something like an insert and an update based on that insert inside of 1 transaction.

Are you referencing running from the SQL Agent? The short answer is no but there are ways to make things work.

If you gave the specific issue you are trying to...

It is a good idea to try to just restart the agent but because SQL server is still running andyour agent is really not running the job only starting it....

I have had this issue before. I have a 24X7 environment too but I just scheduled a maintenance window. You can just explain SQL Server is not meant to be...

Do you have a test enviorment that you could test it in?

It should be OK as long as you are only reading from the table.

You also created the "tools" folder?

Does the user exist on the remote server?

Do you get the same failure if you run the instalation from CD?

All logins or just a subset?

You can import the data to sql server in to 1 big VARCHAR field then use REPLACE to replace the ^ with something useful like a comma. Then Export the...

I would also check to see if your DTS package transformations have been changed. It is easy when you highlight a column to scroll on your mouse which will cause...

You could also write a script to KILL all connections to the database then put the database in a READ ONLY Mode.

You could also put a TABLE LOCK on the...