I think its just difference in syntax from 2000 to 2005.

Is the file on your local C drive or on the C drive of the server?

try doing an master..xp_cmdshell 'dir C:\test\' in query analyzer and check if you can...

In your code you are already committing the transaction before checking for @@error?

Also, your DELETE is locking up the table for the INSERTS. Hence the 'suspended' state.

Also you might want...

Never run Profiler on Production serers. You could end up rebooting your box. Check out PSSDiag utility from MS. Run SQLDiag, get the info and analyse it.

Am not sure if you can set up replication from 2000 to 2005. Perhaps TLog shipping can be of interest to you until your migration is complete?

It does make a difference. Check out the query plan set stats IO on and you can see for yourself.

Update dbo.tablename

SET email_address = Replace(email_address, '@emailaddress.net', '@newemailaddress.net')

Syntax:

REPLACE(string, , )

Before you do an UPDATE, you can do a SELECT

SELECT email_address , Replace(email_address, '@emailaddress.net', '@newemailaddress.net')

FROM dbo.TableName

to see which rows get updated.

Have the profiler running and load all the traces into a table. Query the table for all procs taking longer or having more reads or taking too much of CPU....

Dont you have a PK on the tables?

Sure:

DECLARE @d DATETIME

SET @d = '2006-10-24'

SELECT DAY(DATEADD(d, -DAY(DATEADD(m,1,@d)),DATEADD(m,1,@d))) AS 'Last day of the month'

If you do SET SHOWPLAN_ALL ON and run the query it tells you where or not the queries were executed in parallel. Generally, not.

yes you can drop the article from the subscription and add it back. SQL will push the entire table to subscriber.

exec sp_dropsubscription @publication = 'Pub_Name'

...

Generally Replication bombs out on schema changes. You can add/drop columns but if you need to alter a column, its best to drop the article from the publication, make the...

We have had the stored proc for years without issues. Suddenly it started going wild. I will check for the query plans. I did think about recompilations but have to...

I cleared the cache, recompiled the proc too. I didnt check the execution plan but I had the profiler on and it kept getting stuck at this DELETE.