This is a very good upgrade article but why it was named "Solving a 401 error" ?

You should not be deleting the column. You may just remove Identity property from the destination or try to enable Identity Insert.

Read this:

http://www.simple-talk.com/content/print.aspx?article=196

The identity crisis in replication

05 July 2005

by Hilary...

High IOs can also be caused by low physical memory, check if something memory-intensive is running, in this case paging can be a reason for the IO activity.

You may want to check what other jobs are running on the server at the same time. We had cases of Antivirus SW, Backup jobs etc contributed to high IO

Does you table have an Identity column?

Please read this:

http://support.microsoft.com/kb/231273

Do you think that your issue may deal with catalog replication? This is the quote from the article:

"Global group membership for a user is evaluated when that user...

I had the same problem with OPENROWSET which is basically a dynamic version of a linked server. OPENROWSET in a stored procedure on one server connected to a number of...

You may want to read this:

http://support.microsoft.com/kb/811889

Article ID: 811889 - Last Review: March 16, 2007 - Revision: 20.9

How to troubleshoot the "Cannot generate SSPI context" error message

You may scroll right to...

I...

I would use any script task that allows to run VBscript.

In VB script I would create an instabce of Excel and use Excel Object model to rename the tab. For...

The best way is to make yourself familiar with the Event Log records (Errors - red, Warnings - yellow, Informational messages - blue) is to run SQL Server and take...

You have to check the Event Log both system and application logs and SQL Server log.

The message about stop request from the service manager means that the SQL Server ...

This is a special character.

There are 2 workarounds in BOL:

http://msdn.microsoft.com/en-us/library/ms179859.aspx

Read in this page under these subtitles:

Using Wildcard Characters As Literals

Pattern Matching with the ESCAPE Clause

Let us know if it helped.

Thanks for the update. Sometimes issues are resolved through the re-install.

I did a nice little experiment:

I scheduled a job to run every 5 min when the job duration is 10 min with retry attempts every 3 min:

Job JobConcurencyTest2

Job Step1

Type; TSQL

WAITFOR...