I have been through this myself and the solution was to Turn HT OFF on HP servers based on Xeon Procs!

Hope this helps.

you need to tell us what do you do for the multiple values of 'h' throught 'z', MIN, MAX,...etc?

EXAMPLE:

nsert into i_tbl(a,b,c,d,e,f,g,h,i...z)

Select a,b,c,d,e,f,g, MAX(h),MAX(i)...MAX(z)

from s_view

group by a,b,c,d,e,f,g

Cheers,

you have to use an stored procedure. SQL Server Functions are not meant for DML.

Did you check that MSDTC is "ON" on the server where it fails ?

SQL Server 2005 *IS* in my opinion the buggiest! Of course is a "massive" change from what 2000 offered

Here is another, if you do defrag don't forget to update statistics when you are done

Modify the appropriate replication stored procedures to do just that ?

sounds like a little bit excessive but If the aim was to minimize restore time then that can explain why.

Hopefully that was the purpose, but if that wasn't you are...

just verify that FTP is *done* by the time BCP starts!

Oh and sp_rev_logins does *NOT* check for windows_policy so if you have a password that won't pass your windows policy the script will fail unless you configure the output to...

you can also modify sp_rev_logins to generate the "DEFAULT_SCHEMA" automatically to "dbo".

It will save you a "ton" of work

On the other hand DBCC INDEXDEFRAG does requires to update the statistics afterwards!

We can argue about "wording" of these things for hours if you want.

The reason M$ used IDENTITY_INSERT ON instead of DISABLE_IDENTITY "hopefully" can justify *my* way of thinking about...

Here is a "start"

http://www.miracleas.com/BAARF/

or:

exec sp_update_resume

followed by

exec sp_distribute_resume