when you restore a 2000 database in a 2005 the compatibility level is automatically 8.0

to verifyit run :

exec sp_dbcmptlevel @dbname = name

And make sure that the drive is "compatible" with the controller you are using ... 😀

Make sure you update your stats with "FULLSCAN" and that you rebuild your indexes.

After that the runaway plans can be revisited I have found only 2 cases in which the...

As long as your filters are "narrow" enough and you are writting to an independent drive you should be fine!

Funny thing is that RAW is what M$ uses for the tcp-E benchmarking.

If you make it too small you may suffer from autogrows so. You should size it properly so that you have the necessary space at all times and you need...

Datamirror

SQL Server Log Shipping

SQL Server Replication

you should ensure that the destination path exists:

restore filelistonly from disk='....'

See if the destination exists. Normally 2005 introduce MSSQL.1 in the path so it may not match the 2000 one...

Tony Rogerson has found that "DISABLING" triggers (at least in 2000) does not disable the underlying performance effect entirely

http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/10/27/1248.aspx

So do NOT trust on Disabling when performance is at stake....

It all depends what are you calling "corrupt" usually when corruption affects the primary replication agents break and you effectively can't transfer "corruption" ...

You are correct on the SWICHT statement. It is not possible to use it because it is supposed to be a minimally logged opperation which LogReader can't understand, like Truncate...

Those Services Operate only on the Local machine and there is no need to change that in fact is possibly the only way to ensure transparent access to VSS.

You should...

CREATE TABLE tbl_PaymhistCurrentWeek

( AcctCode AS ISNULL(SUBSTRING(AcctCodeWithZeros, PATINDEX('%[^0]%', AcctCodeWithZeros), 14),''),

Co char(2) Not Null,

AcctCodeWithZeros varchar(20) Null,

CONSTRAINT PK_PaymhistCurrentWeek Primary Key Clustered

(AcctCode, Co)

)

Insert into tbl_PaymhistCurrentWeek (Co, AcctCodeWithZeros) VALUES ('C1','0000123')

Insert into tbl_PaymhistCurrentWeek (Co, AcctCodeWithZeros)...

Also make sure you don't do just one INSERT per row but per "multiple" rows.

Can you post the DDL of the table ?