Hello,

I have a web service that reads its web.config file to connect to an Oracle
database.  There are a number of methods in this socalled BACKBONE that
either send inforomation to or from the database.  That works great.

I have the INTERFACE which is what the user sees.  When the page is first
navigated to, it creates an object of the BACKBONE and calls certain Web
Methods to get data so I may populate dropdown lists and such.

That works great too.  :-)

However, my DBA wanted me to set an action for each "program" that connects
to his database.  I can create this "action" no problem.  The only issue is
that it happens to create 11 entries/connection to the database.  Bascially 1
for each of the 11 seperate calls I make to the BACKBONE.

I thought I could just create the connection in the BACKBONE's Global.asax
file as a session variable and use it when I need to connect to the DB but
that had no difference.  Still 11 connections.  I understand that the web
service simple is being called 11 seperate times.

My question is, is there any way to keep that web-service open?  Or some way
of at least storing the connection in a session variable that will stay?  I
have to believe I am not the only person creating a Web Service to do all of
the DB grunt work.  Are we all wasting connections and the overhead of
connections connecting?  Am I missing something here?

Please help,
Thanks in advance