JDBC vs .NET?
Stupid question.
My developers are asking a question that we can not seem to answer and I am hoping it can be answered it here. We have been heavily involved in developing a OCI Connection Pool rather that a Connection Cache Pool which is the default in VB.NET. Cache Pool will open a dedicated connection every time you open a connection to the database whereas an OCI Connection Pool will open only one dedicated connection and use session connections (PSUEDO) which is ideal for performance and manageability not to mention a better practice, but in VB.NET we can not seem to do this. I have posted help questions on this matter on many different forums over the web but no really good answers.
After reading online and through many Oracle manuals and documentations, I have read that JDBC is the ONLY way to accomplish this task (OCI Connection Pooling). I refuse to believe this but who am I to argue this. My question I am asking you, my peers is:
-Is there a way to use JDBC in a VB.NET application as our method to connect to the DB, but I would like to use VB.NET to retrieve any data requested by the application? I already have the Java code to create a OCI Connection Pool but we have a VB.NET application, and we want to use this to view data.
-Can JDBC establish a connection to the DB through VB.NET (either by calling this Java app from the VB.NET app or something like that) and only that and get the data through whatever means in VB.NET or to retrieve data, has to be Java? If JBDC can establish the connection and allow .NET to get data, how does this work?
I greatly appreciate your help and advice.