Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Oracle connection to with Linked Database

Status
Not open for further replies.

cmmrfrds

Programmer
Feb 13, 2000
4,690
US
I am connecting to an oracle instance called inst1 which has a linked database to another oracle instance called inst2. I can write SQL when connected to inst1 and join to tables in inst2 using the multi-part syntax and this is good, but...... I would like to see the tables in inst2 when connectioning my Crystal Report 11 to inst1. I only see the tables and views in inst1. How can I see the tables in inst2 in the Crystal Connection? I guess one alternative is to make views in inst1 that reference the tables in inst2, but I want to avoid this if possible. I am connecting thru the native oracle connection and we are prevented from using ODBC in our company. Need to use the native connection or possibly OLEDB.
 
Hi,
The only way ( other than views) to do that is to have 2 connections, 1 to each instance..




[profile]

To Paraphrase:"The Help you get is proportional to the Help you give.."
 
Thank you for the input.

To have 2 connections defeats the purpose of what I am trying to achieve, that is when the name of inst2 changes to inst2X I don't need to go into each report and update the connection information. With the linked database the DBA can just change the name in that object. The other problem is that the joins between tables in the 2 instances would be done on the Crystal side which would be unacceptable for performance.

I did talk to BOXI tech support and they told me that the database link object would be exposed using ODBC, but they didn't seem to want to dig into how to it with the native oracle driver, or if was even possible.
 
Hi,
Looks like views are what is needed..that way everything is done on the database side.Is there some reason you want to avoid these?





[profile]

To Paraphrase:"The Help you get is proportional to the Help you give.."
 
I wanted to avoid since creating the view puts the DBA in the middle each time I need a new view especially on new ad hoc requests that cannot use a view already created. My other option is to do use the linked database syntax in SQL and create a Command Object instead of linking the tables in the report. I am leaning in that direction since it puts it all under my control.

Thank you.
 
Hi,
Yes it does..
The Command Object is treated like a view except that it does not become a database object so your DBA should be OK with it..
(Unless, of course, you do a bad join(s) and get some enormous cartesian product that brings Oracle to its knees..[wink])


[profile]

To Paraphrase:"The Help you get is proportional to the Help you give.."
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top