Posted by Dan Guzman on 03/11/06 15:52

Ryan,

I hope Alexander's staging table work-around works for you. That's what I
would do.

I lost the script/file I used to repro your problem and can't seem to
recreate the error. Please post a script that can be used to reproduce you
problem.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"Ryan" <ryanofford@hotmail.com> wrote in message
news:1141916168.932188.200460@i40g2000cwc.googlegroups.com...
> Should have mentioned this is in 2000.
>
> One problem is that we can't truncate the data as it's not ALL of it
> that is being replaced, just a small chunk. The two statements are
> being called sequentially and has only reared it's head recently. We do
> have a way around it as I mentioned, but there must be a better
> approach to this instead of calling a second method if there is an
> error.
>
> The data is not duplicated as I can run the two parts seperately and
> they are fine. Manual checks also confirm this.
>
> Ryan
>

[Back to original message]