Oracle client?

I'm using the Oracle data connector within Reporting Services because it uses
the Oracle client, which should be the most efficient.
There is very little description/documentation I can find in Reporting
Services help about this connector and it is difficult to figure out what it
is doing and what connection parameters it supports. Is it documented
anywhere?
For example, I tried to set the connection pool information in the
connection string (using the same properties as described in the ODP.NET
documentation), but for the oracle server log, it doesn't seem to be using
them correctly.
At this point I'm am considering writing a DPE for ODP.NET, just to make
sure I have that control.
Brendan.ODP.Net is not being used. Microsoft managed provider is being used. The
provider requires 8.1.7 or higher client to be installed I believe. It gets
even more confusing though. If you use the graphical query designer (4 pane)
it uses OLEDB. If you use generic query designer (2 pane) it uses the
managed provider. When you are at runtime it uses the MS managed provider
for Oracle. My suggestion is to always use the generic query designer so you
are developing with the same provider that you will be running under.
Hopefully this will get more clearcut with the next release (November).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Brendan Whelan" <BrendanWhelan@.discussions.microsoft.com> wrote in message
news:94800733-02F7-4D4D-9782-72CADEC7FE6E@.microsoft.com...
> I'm using the Oracle data connector within Reporting Services because it
> uses
> the Oracle client, which should be the most efficient.
> There is very little description/documentation I can find in Reporting
> Services help about this connector and it is difficult to figure out what
> it
> is doing and what connection parameters it supports. Is it documented
> anywhere?
> For example, I tried to set the connection pool information in the
> connection string (using the same properties as described in the ODP.NET
> documentation), but for the oracle server log, it doesn't seem to be using
> them correctly.
> At this point I'm am considering writing a DPE for ODP.NET, just to make
> sure I have that control.
> Brendan.
>|||I use oracle and SRS now with no problems. you just have to install the
oracle client on the SRS server and configure a service using net manager.
once you can get to oracle using Sql plus then you can use the client to
connect to oracle. This is the fastest way using the native Oracle client.
Bruce L-C [MVP] wrote:
>ODP.Net is not being used. Microsoft managed provider is being used. The
>provider requires 8.1.7 or higher client to be installed I believe. It gets
>even more confusing though. If you use the graphical query designer (4 pane)
>it uses OLEDB. If you use generic query designer (2 pane) it uses the
>managed provider. When you are at runtime it uses the MS managed provider
>for Oracle. My suggestion is to always use the generic query designer so you
>are developing with the same provider that you will be running under.
>Hopefully this will get more clearcut with the next release (November).
>> I'm using the Oracle data connector within Reporting Services because it
>> uses
>[quoted text clipped - 15 lines]
>> Brendan.
--
Gene Hunter
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200508/1