Re: CoInitialize failure with many processes

Is this typical of each of the hundreds of processes? So it is using ADO to
connect to a SQL Server?

I could not find a good reference about ADO connection pooling, but I
believe the pool is process specific. In other words, each process will get
its own connection to the SQL Server. I can see how having hundreds of
simultaneous connections to a SQL Server might be a bad idea.

"netstat -o" at the Command Prompt will reveal what is going on with TCP
connections in practice. You can try different parameters to get whatever
information you want.

I would think some more about how you might reengineer this a bit without
using up too much time that you don't have.

Paul

"Dan" <Dan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BE92EC61-A5B2-4D2F-845F-BCEC7BE6D8B3@xxxxxxxxxxxxxxxx
Brian,

As I continue to dig through this code, it appears that it is using COM to
directly communicate with the SQL server. I'm learning as I go here.

Prior to calling CoInitialize(NULL), there is nothing done of interest.
(e.g. Setting thread priority, parsing command line arguments, etc) After
the CoInitialize, the connection is made using a msado15.tlh file and a
_connection object (apparently an ADO object, or ActiveX Data Object).
CreateInstance is called on a _ConnectionPtr object, then Open is called
on
this object with the following connection string:

"Provider=sqloledb;Server=%*.*S%S%*.*S;Database=%*.*S%SSystem;Trusted_Connection=Yes;"

The resulting object is returned as a _variant_t object casted from an
(IUnknown*) pointer. This variant object is passed into a _RecordsetPtr
object's Open function along with an SQL statement casted as a _variant_t
object as well.

Regarding the Performance Monitor, I haven't seen anything out of the
ordinary. What performance objects and counters should I be looking at?

Thanks,
Dan

"Brian Muth" wrote:

Ok, forget trying to create winstations. Kick your co-worker in the pants
for wasting your time.

Can you please clarify the picture for me. You are trying to create
hundreds
of processes. Each process is instantiating a COM object. So, is the COM
server a DLL or a separate executable? Is it a simple COM object or a
full-blown ActiveX control? Was it developed in MFC or ATL? What
resources
does it use?

Please try to answer as many of these questions as you can. And did you
run
performance monitor yet as advised?


Brian



.

Relevant Pages

  • Re: Sql Server 2000 slow
    ... If I close the connection (moving the Open/Close ... ADO) and the dll gives twice the performance. ... > Are there any known performance issues with .NET accessing Sql Server ...
    (microsoft.public.dotnet.framework.performance)
  • Re: Cross Transactions between ADO & ADO.Net
    ... MARS session pool limited to one connection?). ... > There is one thing that might help here, if you're using SQL Server. ... We even call ADO code from ... >> the DTC cordinator from COM+ to handle the transactions between ADO.Net ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SQL Server extremely slow
    ... my personal experience with a similar setup as your (Sql Server ODBC ... against the sql server (ADO was specifically designed for use with sql ... the connection is closed. ...
    (comp.databases.ms-access)
  • Re: absolute newbie question - connecting to SQL server in ADO.net
    ... How do I get the above connection working? ... > experience of ADO prior to this was in Access 2000. ... Have I wasted my money buying VB.net standard because it can't connect to ... > an SQL server 2000 server? ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Error "SQL Server does not allow remote connections"
    ... The application could not connect to the sql server db. ... network is blocking the connection. ... SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 ... integratedSecurity, SqlConnection owningObject) +737554 ...
    (microsoft.public.dotnet.framework.aspnet)
Loading