all groups > sql server msde > march 2005 >
You're in the

sql server msde

group:

How many recordset open ?


How many recordset open ? Sylvain Aufrère
3/14/2005 8:01:06 AM
sql server msde:
Hello,

I use VisualBasic 6, MSDE and ADO2.8.
I seek to know how many recordsets are open at the same time.
How much CPU (or memory) use they?
My goal is to know if all my recordset is well closed.

Re: How many recordset open ? Andrea Montanari
3/14/2005 5:23:40 PM
hi Sylvain,
[quoted text, click to view]

I do not know counters for such questions...
you can see active connections to the SQL Server instance, but not
recordsets, as they are part of the ADO design (better, the ADO counterpart
of OLE DB Rowsets)
and I do not think you should inspect for memory allocation/requirements in
order to check your clean-up code... you just have to review it and verify
you properly close and release objects as it should be
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply

Re: How many recordset open ? Sylvain Aufrère
3/15/2005 12:19:03 AM
Thank you Andrea,

Ok, there is nothing to see open recordsets.
But, which tools allows seeing the application activity on MSDE data base ?
Which tables is opened? read? written? Who? When?

My goal is to know if my development team correctly releases the data base
objects.
I seek a "systematic" method to check that.

Thank-you to reply to these newbies questions !

[quoted text, click to view]
Re: How many recordset open ? Andrea Montanari
3/15/2005 5:16:34 PM
hi Sylvain,
[quoted text, click to view]

you can perhaps monitor active connections both via Enterprise Manager or by
executing sp_who filtering out for you required database...
actually read write operations depend on user's activity... if your user
form is simple waiting for user input you'll see no db activity at all...
tables are not opened... they are read and eventually written... they can
even bre read from cache as SQL Server try to keep them alive on cache once
read... writing conditions depends on database recovery model too, as dirty
pages can be flushed to the transaction log and stay there untill a backup
log or, with simple recovery model, be flushed to data pages at recurring
checkpoints...

[quoted text, click to view]

you can perhaps use the SQL Server Profiler running traces, and/or ad a
specific SQL Server counter on the System Monitor...
have a look at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_mon_perf_76cm.asp
for further info... and all counters are successively exploded..

but I do think the best check is code review...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply

AddThis Social Bookmark Button