Of course you need to have the ORACLE client installed on the SQL Server
database server (with an appropriate TNSNAMES) as well to get option 2 to work.
Toad for Oracle also comes with Toad for Data Analysts, which can connect to
both Oracle and SQL*Server and has some pretty good facilities for automating
transfer processes. I’d recommend looking at that. It’s how I’m handling such
things.
Thanks Jim for the quick response. The funny thing is we purchased the Toad for
Data Analysis & Data Modeler two years ago and I installed them on my PC but
unfortunately haven’t had a chance to touch them yet because I thought that are
developers tools . I knew it has a nice function to access/to load data from
difference sources/platforms. I’ll try to learn how to.
How big of a deal is this kind of thing - moving data between Oracle and SQL
Server?
It probably wouldn't be that tough to use ODBC as a destination for
grid->rt-click->Export DataSet, or as a source for "Import Table Data".
The only downside to that is I'd have to use ODBC, which gives me the
heeby-jeebies.
And it should, although MS themselves have said that it's the future of DB
connectivity, even making an SQueaL Server ODBC driver on Linux.
That being said, if I do have a need for a 1-time data transfer like this, I
turn to Toad for Data Analysts. Since it's included with Toad for Oracle,
it would seem somewhat redundant, no?
Yeah there are ways around it. Just wondering how common it is, and would it be
worth the convenience of having it in Toad, where you can set it up as an
action, etc.
Personally I’m looking for a way to automate a data flow, but our idea of
automation is to have the databases talk to each other, not to schedule
something in Toad; so for my personal purposes adding something to Toad is not
worth the effort.
Nate Schroeder
Enterprise Services - Data Management Team
Monsanto Company
800 N. Lindbergh Blvd. LC4D - Saint Louis, MO - 63167
Yeah, in my case there are too many corporate firewalls on both sides of the
transfer. (One government agency, one large bank).
No way could I ever get through the paperwork to do a direct connection between
the servers.
And the data quantities are generally fairly small (thousands of rows, not
millions). So TDA works great, since I have client access to read the SQL*Server
source and write to the Oracle target.