Mistery between SQL Express and Workgroup Edition
-
I've a problem for long time with dirty reads of data, finally i've seen that the problem is only in SQL Server 2005 Workgroup Edition not in Express Edition
I've test the same thing in booth editions with the same database with this result , any ideas?
IN the image attached is SQL Server 2005 Workgroup Edition not works correctly.
IN the image attached is SQL Server 2005 Workgroup Edition works correctly.
Is the same database
Thks, in advance for the ideas...
David.
-
New investigations.
seems ocur only in static cursors , searching with not static cursor , works well.
-
if you use "dirty reads" you allow your applications to use uncommitted data !
No complains are accepted for that ! :unsure:
Cursors can cause the need to be materialized in temdb, hence when using dirty reads, this dirty data is being materialized in your cursor info.
Dynamic cursors will try to get the data only at the time the application fetches it ! If the trx is being rollbacked in the time between, ...
Check out " TRANSACTION ISOLATION LEVEL " in books online.
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
Hello,
I'm using read committed isolation level, but is this case, the important thing is that the same application, the same database , the same isolation level, with diferent versions of SQL Server 2005 , causes diferents results.
if you see the first image with the same isolation LEVEL , the same moment and the same data, the firts select read dirty reads , and the others no , and only happend in WorkGroup Edition not in Express Edition.
I've solved mi problem using ctKeySet cursor in mi ado application , but i thing for a moment that is a Big bug from SQL Server 2005.
thks.
-
Indeed strange findings.
I think the best way to tackle this problem is to use sqlprofiler to capture the load launched on both engines (FULL).
Especially check the connections settings to actually figure out the used connection isolation level.
Also keep in mind isolation levels can be set at ado.cmd level !
Are your engines up to date with the service packs ?
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
Hello,
Yes i've the SP3 installed in all SQL servers , the program in the images (for the tests) is nothing especial , is the SQL Server Management studio.
I've test it in 5 diferents servers with Workgroup edition , and 5 diferent servers with Express edition , with the same result.
In mi Delphi+ADO application it works well changing de cursor type to ctkeyset in read only datasets.
But i've post it because , the error exists , and is very preoccupying.
regards.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply