Author |
Topic |
jason123456
Starting Member
8 Posts |
Posted - 2011-12-02 : 02:33:20
|
I used mdb ADODB connect to msql server run run storage procedure download data around 50 number of row.Sometime, the regional user download data miss a few row.I can't simulate the issue.The table size around thirty thousand data and sql simple join with 3 table.I tried every step completed then save in log table. But it seems normal.Does anyone know whether any limitation on driver or sql sever ? |
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-12-02 : 03:09:59
|
are you sure the rows are not getting missed due to joins? please check if you've coresponding values existing in joining tables first.------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
Kristen
Test
22859 Posts |
Posted - 2011-12-02 : 04:54:16
|
Are you using the WITH (NOLOCK) hint, or an isolation level that allows dirty reads of uncommitted data ?If you are using a Stored Procedure maybe have it "cache" the results to a table, and then you can review whether the data was correct (and thus the ADODB layer, or application, "lost" some rows), if not you will know its something in the Query itself. |
|
|
jason123456
Starting Member
8 Posts |
Posted - 2011-12-04 : 20:02:24
|
Yes , it was used nolock hint, but i checked in db that data updated.I don't understand nolock issue. |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-12-04 : 23:45:35
|
quote: Originally posted by jason123456 Yes , it was used nolock hint, but i checked in db that data updated.I don't understand nolock issue.
nolock will cause some of uncommited rows to be also returned. If transaction rollback afterwards you wont have the rows actually present in resultset which is why you see 'missing rows'see below for an alternativehttp://visakhm.blogspot.com/2010/02/avoiding-deadlocks-using-new.html------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
jason123456
Starting Member
8 Posts |
Posted - 2011-12-06 : 02:52:56
|
thanks your advice , i checked all data committed at the mourning , then storage procedure run at night. , is it any gap in region side?I am checking the sql any hints. |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-12-06 : 03:55:49
|
sorry didnt get what you're asking for. DO you mean you see a gap in data at night? may be some deletion/purge operation might have happened in between------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
jason123456
Starting Member
8 Posts |
Posted - 2011-12-06 : 04:39:20
|
can i open the log monitor specific store procedure and table? |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-12-06 : 04:50:53
|
you cant do it now for stored procedure runs that happened already. you can however run profiler next time procedure runs and monitor to see what processing is happening at backend------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
jason123456
Starting Member
8 Posts |
Posted - 2011-12-06 : 04:55:08
|
i mean , i checked all data committed in the mourning any storage procedure run at night.it shouldn't have nolock issue. is it right ?i didn't know what's gap now.And how to check gap ?is it between sql server , network or driver? |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-12-06 : 05:00:05
|
nope...nolock issue happens only while executing codeNo idea on gap though...I suspect it may be caused due to some other purge activity that happened in interim------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|