SQLDMO and server.Disconect
From: Eladio J (namrek1_at_hotmail.com)
Date: 01/30/05
- Next message: Bob Barrows [MVP]: "Re: need help: new at store procedure"
- Previous message: moshe: "need help: new at store procedure"
- Next in thread: oj: "Re: SQLDMO and server.Disconect"
- Reply: oj: "Re: SQLDMO and server.Disconect"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 31 Jan 2005 00:07:21 +0100
Hi,
I'm using SQL-DMO to view some properties from a SQL Server instance; I have
a doubt about the results I see in profiler and I hope that any of you can
help me with my question;
When I connect to the instance I use the method Connect and when I finish I
use the method Disconnect from the SQLDMO.SQLServer2 object. I see in
profiler the Audit Login and Audit Logout events and I don't see that the
process stays in sysprocesses, but every time I Connect/Disconnect, the
Application Name in Profiler is changed ( SQLDMO_1, SQLDMO_2, SQLDMO_3, ...)
Do you know any part of EM that uses DMO to see if the same behaviour is
reproduced?
Do you know if I can set the Application Name in the same way that we can do
now with the method ApplicationName in the ADO.NET object Connection?
I was worried about the different Application names in profiler because it
looked like the connection remains open, but seeing sysprocesses the
connection is dropped.
I know that DMO do not use connection pooling, can it be a SQLDMO "mecanism"
to avoid the connections reuse?
Thank you,
Eladio J
- Next message: Bob Barrows [MVP]: "Re: need help: new at store procedure"
- Previous message: moshe: "need help: new at store procedure"
- Next in thread: oj: "Re: SQLDMO and server.Disconect"
- Reply: oj: "Re: SQLDMO and server.Disconect"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|