Check if using ROWLOCK hint helps...

Modify your script to drop the table explicitly at the end otherwise your tempdb will choke if you have multiple users creating objects in tempdb and they are not dropped...

You need to use dynamic SQL. Something like this:

declare @fileg varchar(60), @sql varchar(500)

set @fileg = substring(CONVERT(VARCHAR, DATEPART(YEAR, GETDATE())), 3, 4)

Set @sql = 'create table dbo.test (id int) ON ['...

You better put it IN the JOIN or use WHERE. example:

from dbo.Orders o

join dbo.Account acct with (nolock) on h.AccountID = acct.AccountID

join sourceOrders aa with (nolock) on h.InvoiceNumber = aa.SourceInvoiceNumber

and...

Isnt the loading process being done during off hours?

I would recommend disabling the replication, do your upgrades, then re-setup replication. You need to configure the distributor first. Look up books online in 2005 for replication setup steps. They...

check out the undocumented proc sp_MSForEachDB

You can get the data in, and run an UPDATE with REPLACE to remove the double qutoes.

Decimal(x,y) is a better option.

Also, note that you can use CROSS APPLY to get the text directly and use it in a JOIN stmt instead of looping through. If your query is executing quickly...

I think you have to drop the indexes and recreate them on the new filegroup.

Usually the dateformatting should be done at the client level. If you need to use the same format irrespective of the client you can specify the SET DATEFORMAT just before...

Try sp_removedbreplication to drop any replication related stuff from the db.

If the table is small, try dropping the article from the publication and add it back and see if you can replicate the error.

In sql 2005 you dont need to use sp_Repladdcolumn. You can just do a regular ALTER TABLE and the table is modified at the subscriber too.