Re: 2nd Request ??'s "Cursors"

>Date: Tue, 29 Nov 1994 10:26:00 -0500 >From: Connie.Balcom@NORTH-SUPPLY.SMNOSUP.LANGATE.sprint.com >Subject: 2nd Request ??'s "Cursors" >X-Informix-List-Id: <list.5091> > I am wondering if anyone has any idea what kind of impact > prepared/declared cursors have on the "SERVER" itself, not the data. > I know that the limit is "256" cursors per Online 5.0 application. I think that was the limit in the previous (4.1x) version; the limit in 5.0x is controlled by the system memory -- though if you managed to get up into the 2 000 000 000 cursors range, you might run into problems too. > If I have "100" prepared/declared cursors per application and "300" > user executing this application, where are the "30,000" cursors > stored at / executed from on the "SERVER"? Each of the 300 users has 1 sqlturbo (since we're talking about version 5; the rules change with version 6 and above), and each sqlturbo has 100 cursors in local (non-shared) memory. The "server" can only mean the oninit process and associated daemons -- page cleaners (tbpgcl), auto rollback (tbundo). These do not store cursors; they manage the shared memory and disk, but not the cursors themselves. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h>