August 4, 2010 at 4:32 am
Hi,
I have a database in SQL Server 2005 that as information that some guys in Oracle need to read.
I told them that their app could connect to our SQL Server and collect all the information they want to and then, their app would store the data in their Oracle Database, but they do not have the knowlegde to connect to SQL Server through the app.
Do you masters have any sugestions?
Thank you
August 4, 2010 at 4:36 am
Depends on the latency requirements and "when" they need the data. Can this be something you transfer to them on a nightly basis using SSIS? Or is this a situation where they need live access?
August 4, 2010 at 4:39 am
They need to have the access to the data, all the time...
August 4, 2010 at 4:43 am
Maybe i can talk to them to receive the information ony once per day, at night...
Do you have any solutions for this two different situations?
August 4, 2010 at 6:20 am
If they need live access you just have to set up a connection either direct through ADO (or whatever) or using another tool such as the Oracle Gateway (it used to be called Transparent Gateway).
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 4, 2010 at 6:25 am
What about if they only need to access data once a day? you where talking about making a SSIS? to do what?
August 4, 2010 at 6:29 am
Brandie mentioned SSIS, which is SQL Server Integration Services. It's the built-in SQL Server ETL (Extract/Transform/Load) tool. She was suggesting that if they could deal with day old data, to set up an SSIS job to move the data on a daily basis, probably during off-hours.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 4, 2010 at 6:52 am
Grant Fritchey (8/4/2010)
Brandie mentioned SSIS, which is SQL Server Integration Services. It's the built-in SQL Server ETL (Extract/Transform/Load) tool. She was suggesting that if they could deal with day old data, to set up an SSIS job to move the data on a daily basis, probably during off-hours.
Exactly. Basically, SSIS could export the data in almost any format and then your Oracle people could create a job to load the data nightly into their database.
Though I haven't dealt with Oracle before, you might also be able to use SSIS to directly load Oracle using one of the available connection managers in SSIS. But that would require access to the Oracle DB.
August 4, 2010 at 8:11 am
Brandie Tarvin (8/4/2010)
Grant Fritchey (8/4/2010)
Brandie mentioned SSIS, which is SQL Server Integration Services. It's the built-in SQL Server ETL (Extract/Transform/Load) tool. She was suggesting that if they could deal with day old data, to set up an SSIS job to move the data on a daily basis, probably during off-hours.Exactly. Basically, SSIS could export the data in almost any format and then your Oracle people could create a job to load the data nightly into their database.
Though I haven't dealt with Oracle before, you might also be able to use SSIS to directly load Oracle using one of the available connection managers in SSIS. But that would require access to the Oracle DB.
You can go directly to Oracle from SSIS. There's even a third party destination available to make it really easy to do.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply