|
|
Posted by Weyus on 06/27/07 20:38
On Jun 27, 2:57 pm, Roy Harvey <roy_har...@snet.net> wrote:
> On Wed, 27 Jun 2007 19:40:12 -0000, Weyus <w...@att.net> wrote:
> >It looks like if I do a
>
> >SELECT blah FROM TABLE WITH (TABLOCK XLOCK)
>
> >at the very beginning of my transaction, that would do the trick
> >right?
>
> >Wes
>
> If you plan on locking the entire table during the load, why not just
> let the IDENTITY value be assigned normally? It seems like you are
> creating a load of extra work for yourself.
>
> Roy Harvey
> Beacon Falls, CT
Because I have two tables, A and B, both of which I need to bulk load.
B has a foreign key to A. A has constraints on it. B has no
constraints.
So I have two files, one for loading A and one for loading B.
If I bulk load A and some of the constraints kick out records, such
that not all of the records load, then when I load B, I will not have
a way to know how to set the foreign key in B correctly.
If I was just loading one table, your point would be totally valid.
Thanks,
Wes
Navigation:
[Reply to this message]
|