Server Side Cursors

Using a server-side cursor (which, by the way, is the default in ADO), the records contained in the recordset are cached on the server. The major benefit of this is that network traffic is significantly reduced, thus improving application performance. The downside is that server resources are consumed for every active client; the more clients (and the more data being cached), the more server resources are consumed. It is important, therefore, to plan ahead to ensure your server has sufficient resources to do the job. Server-side cursors allow you to use both keyset and dynamic cursors, and also support direct positional updates, which are fast and avoid update collisions.

You can also use each connection for more than one operation. For example, you can have a recordset open and still execute multiple update queries without having to open an additional connection. Server-side cursors are best for inserting, updating, and deleting records, and they also allow you to have multiple active statements on the same connection.

0 0

Post a comment