SQL Server problem (transactions <-> fetchall)
Posted: Wed 01 Oct 2008 14:48
In another forum I found this:
---
In practice, transactions and FetchAll = False are incompatible. The only exception if you open DataSet with FetchAll = False, perform fetch completely and only then started calling StartTransaction or Edit..Post.
---
It looks like this problem is also there with UniDAC.
Now I remember that FetchAll causes problem with big result sets. On the other side, I want to use transactions to have better performance for huge update tasks.
Is there somebody, who can share his experince on this topic with MS SQL Server? Is it possible, that this problem is solved in newer versions? We still use SQL Server 2000.
cu Christian
---
In practice, transactions and FetchAll = False are incompatible. The only exception if you open DataSet with FetchAll = False, perform fetch completely and only then started calling StartTransaction or Edit..Post.
---
It looks like this problem is also there with UniDAC.
Now I remember that FetchAll causes problem with big result sets. On the other side, I want to use transactions to have better performance for huge update tasks.
Is there somebody, who can share his experince on this topic with MS SQL Server? Is it possible, that this problem is solved in newer versions? We still use SQL Server 2000.
cu Christian