Very Computer

by **Tom** » Fri, 17 May 2002 10:36:59

Hello...I hope some one can help. I have this procedure
that has a Cursor that returns about 11407 records. I
Fetch the first row innitially and go right into my "WHILE
(fatchstatus=0)" loop and fetch next. In this loop I have
two Insert statements. On my one machine 2000 Pro/SQL 2000
client/256MB of RAM.....on this machine the the Fetch runs
through all rows....for the loop...thus Fetch_status is
always = 0 during the WHILE statement up to the end of the
record. NOW on my other machine NT 4.0/SQL 7.0
client/256 MB of RAM...for some reason the fetch fails
after 214 rows...and I have to run it again to finish the

machines....for some reason the fetch is failing on this
partiular machine.....why? Help!

by oj » Fri, 17 May 2002 14:43:34

exec sp_lock to see if you have block/lock. you might want to post
simplified ddl+sample data+code here. someone might have a solution for you.

--
-oj

http://www.rac4sql.net

http://vyaskn.tripod.com

> Hello...I hope some one can help. I have this procedure
> that has a Cursor that returns about 11407 records. I
> Fetch the first row innitially and go right into my "WHILE
> (fatchstatus=0)" loop and fetch next. In this loop I have
> two Insert statements. On my one machine 2000 Pro/SQL 2000
> client/256MB of RAM.....on this machine the the Fetch runs
> through all rows....for the loop...thus Fetch_status is
> always = 0 during the WHILE statement up to the end of the
> record. NOW on my other machine NT 4.0/SQL 7.0
> client/256 MB of RAM...for some reason the fetch fails
> after 214 rows...and I have to run it again to finish the

> machines....for some reason the fetch is failing on this
> partiular machine.....why? Help!

by **Tom** » Fri, 17 May 2002 22:08:41

thank you...I will check that out....here is an example of
my T-SQL code that the fetch is failing for on the NT
machine but works for the 2000 pro machine.

>-----Original Message-----
>exec sp_lock to see if you have block/lock. you might
want to post
>simplified ddl+sample data+code here. someone might have
a solution for you.

>--
>-oj

>http://www.rac4sql.net

>http://vyaskn.tripod.com

>> Hello...I hope some one can help. I have this procedure
>> that has a Cursor that returns about 11407 records. I
>> Fetch the first row innitially and go right into
my "WHILE
>> (fatchstatus=0)" loop and fetch next. In this loop I
have
>> two Insert statements. On my one machine 2000 Pro/SQL
2000
>> client/256MB of RAM.....on this machine the the Fetch
runs
>> through all rows....for the loop...thus Fetch_status is
>> always = 0 during the WHILE statement up to the end of
the
>> record. NOW on my other machine NT 4.0/SQL 7.0
>> client/256 MB of RAM...for some reason the fetch fails
>> after 214 rows...and I have to run it again to finish
the

both
>> machines....for some reason the fetch is failing on this
>> partiular machine.....why? Help!

>.

example.sql
3K Download

by **Kun Cheng [M** » Thu, 23 May 2002 02:25:42

I believe it's caused by blocking. Why it doesn't happen on sql 2k could be
that locking behavior is changed. Run blocking script and profiler trace to
see if blocking does happen.

Q271509

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Content-Class: urn:content-classes:message

| Subject: Re: Cursors/Fetch Failing on NT 4.0 machine
| Date: Thu, 16 May 2002 06:08:41 -0700
| Lines: 156

| MIME-Version: 1.0
| Content-Type: multipart/mixed;
| boundary="----=_NextPart_000_43C2_01C1FCA0.20671D00"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcH82szFmWLc3gPLQBen/5/C4E6kPA==
| Newsgroups: microsoft.public.sqlserver.programming
| Path: cpmsftngxa07
| Xref: cpmsftngxa07 microsoft.public.sqlserver.programming:258342
| NNTP-Posting-Host: TKMSFTNGXA10 10.201.226.38
| X-Tomcat-NG: microsoft.public.sqlserver.programming
|
| thank you...I will check that out....here is an example of
| my T-SQL code that the fetch is failing for on the NT
| machine but works for the 2000 pro machine.
|