Client vs Server Cursor - Pros/Cons?
From: Bob Dalton (bob.dalton_at_removeme_digitallogistics.com)
Date: 10/17/04
- Next message: Brian Bushay TeamB: "Re: Problem with MS SQL + ADO + BLOB image"
- Previous message: Glynn Owen: "Re: TADOQuery"
- Next in thread: Brian Bushay TeamB: "Re: Client vs Server Cursor - Pros/Cons?"
- Reply: Brian Bushay TeamB: "Re: Client vs Server Cursor - Pros/Cons?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 17 Oct 2004 16:20:27 -0500
I have an application that support eithers MS SQL Server OR MS Access Jet
databases depending on the user configurable connection string.
There is a lot of data involved and I am using TADODataSet components.
Performance is slow, especially with MS Access.
I understand that I can set the ADOConnection1.CursorLocation (which
supports my TADODataSets) to clUseServer instead of clUseClient to improve
performance significantly but I have some reservations as apparently
clUseServer comes with some functionality differences which are not well
explained/documented.
I would like to improve performance by using clUseServer but do not fully
understand the repercussions this might bring with my app.
Can anyone explain this and the pros and cons?
BTW the applicaiton is designed to work on a LAN.....
Regards;
Bob Dalton
- Next message: Brian Bushay TeamB: "Re: Problem with MS SQL + ADO + BLOB image"
- Previous message: Glynn Owen: "Re: TADOQuery"
- Next in thread: Brian Bushay TeamB: "Re: Client vs Server Cursor - Pros/Cons?"
- Reply: Brian Bushay TeamB: "Re: Client vs Server Cursor - Pros/Cons?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]