|
|
Posted by Jack Vamvas on 09/29/02 12:01
Without seeing exactly what your code /configuration is like: You could try
such things as :
1)BULK INSERT strategy.
2) use of TABLOCK
3)Potentially change to Simple Recovery (although I strongly warn you to
consider whether this is acceptable)
4)Break the BULK INSERTs into smaller chunks
--
Jack Vamvas
___________________________________
Search IT jobs from multiple sources- http://www.ITjobfeed.com
<quincy451@yahoo.com> wrote in message
news:31d1158d-719e-4f79-95ee-9de6e2b9f244@p69g2000hsa.googlegroups.com...
>I am running MS SQL 2000 server. The table involved is only about
> 10,000 records. But this is the behavior I am seeing.
>
> The local machine is querying the table looking for a particular
> record. Everything works fine.
> The remote amchine goes to clear the table and then insert all 10,000
> records, into the table the following happens.
>
> 1) the local machines queries do not compilete until the remote
> machine is done.
> 2) the remote machine can take up to 6 minutes to do these 10,000
> insert operations. So nothing on the local machine works right for
> these 6 minutes.
>
> I do not have access to the remote machines source to see what is
> running but I am told it is simply a for loop with a insert query in
> it. Nothing of a locking natture.
>
> Any idea the types of things I should look for to track this down? I
> found this by doing SQL profiler profiling and finding the remote
> operations. Turn these operatiiosn off and the local machine works
> fine again, with no other action.
>
> Thanks,
> David
Navigation:
[Reply to this message]
|