On Apr 29, 3:35 pm, Roy Arellano <r.arellano6...@gmail.com> wrote: > Looking for suggestions on best practices when using a single ODBC > connection to handle multiple connection requests.... > > Scenario: Have tool which gathers data from mulitple databases to > build a multi-dimensional view (reporting). The tool connects using a > single ODBC connection which creates a bottle-neck. Any suggestions on > how to mitigate this so that their is increased connectivity for all > jobs? > > Thanks.
This is going to sound snarky but it honestly not meant to be ... Without knowing the tool that is being used and if the use of a single ODBC connection is a hardwired thing or if it is configurable it is very difficult to answer that question. For instance, I use Excel a lot to create pivot tables from data that I am pulling from our data warehouse and Excel seems to be limited to only opening one ODBC connection at a time which gets a little annoying when I have a workbook that has several queries in it that will only run one at a time. Happily, the powers that be have finally blessed our purchase of OBIEE+ so that will soon be a thing of that past. But i digress. My point is ... you have to find out if your tool will allow you to pool connections somehow or if it is, like Excel seems to be , completely single threaded when doing queries. Sorry not to be of more help but ... there you go Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Oracle PL/SQL" group. To post to this group, send email to Oracle-PLSQL@googlegroups.com To unsubscribe from this group, send email to oracle-plsql-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Oracle-PLSQL?hl=en -~----------~----~----~----~------~----~------~--~---
