ADOMD.Catalog versus ADODB.Connection

[gradley]

We are trying to determine what is the best way to open a connection for an ADOMD.Cellset. I have seen sample code that uses ADODB.Connection on several occasions. We are using SQL Server 2000 Analysis Services with Visual Basic 6.0 DLL's in COM+.

We currently use the ADOMD.Catalog class which I realize has fewer parameters and only allows you to set the ActiveConnection. It does not allow you to explicitly open and close the connection. All of our DLL's are run within COM+ on the web server and therefore share Database connection pooling. In an effort to clean up our code and free up connections, I am looking to use ADODB.Connections and close them upon completion of each component process.

If anyone has knowledge of the pros and cons of each connection type, I would greatly appreciate your feedback.


Thanks in advance,

Gordon Radley

 

[MDXer]

a quick google turned up a few links and this looks like it might be the most informative, even though it is an old article. THis is probably something that is best suited on an enviroment by enviroment basis and may require experimenting. I recall reading more than one where ado and ado md results sets havew differed for the same query, not sure why it happened or if it was human error.

http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/en/wc102202/wct102202.asp

good luck!

"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck

 

[gradley]

Thanks MDXer!

I will review this document.