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!
Data Migration from Paradox to Ms SQL Server and Oracle 9i
- Thread starter ht055
- Start date
ht055,
It's a pretty complex topic, depending on the data you're working with, your experience with the remote databases, and what you're hoping to accomplish.
If all you're trying to do is move the actual tables to an existing remote database, it can be as simple as Table | Copy from the Paradox table to the remote alias. However, for best results, you need to carefully review the structure of your Paradox tables to make sure that your remove server will support similar datatypes, the field names, and so on.
An introduction to the various concepts and issues involved can be found at
Certain versions of Borland's development tools (Delphi, C++ Builder, etc) include a utility called Data Pump that helps you do this, but I don't recall whether it's included with the BDE that Corel provides as part of Paradox.
Hope this helps...
-- Lance
It's a pretty complex topic, depending on the data you're working with, your experience with the remote databases, and what you're hoping to accomplish.
If all you're trying to do is move the actual tables to an existing remote database, it can be as simple as Table | Copy from the Paradox table to the remote alias. However, for best results, you need to carefully review the structure of your Paradox tables to make sure that your remove server will support similar datatypes, the field names, and so on.
An introduction to the various concepts and issues involved can be found at
Certain versions of Borland's development tools (Delphi, C++ Builder, etc) include a utility called Data Pump that helps you do this, but I don't recall whether it's included with the BDE that Corel provides as part of Paradox.
Hope this helps...
-- Lance
- Thread starter
- #3
Hi Lance,
I have current system running on the Paradox. Due to data increase tremedously, so management decide to migrate into the SQL Server 2000 or Oracle 9i. Before decide which database to be used, management want to know which is easier way to do it and with minimum impact.
Could you advice on it? I noticed that we can't migrate the form and report and query into SQL 2000. About the Oracle, there is a form and report tools. I have not idea whether it can be direct port over into Oracle.
Kindly adivce.
Thanks for the information but I need more implementatio/migration information on how to do it.
I have current system running on the Paradox. Due to data increase tremedously, so management decide to migrate into the SQL Server 2000 or Oracle 9i. Before decide which database to be used, management want to know which is easier way to do it and with minimum impact.
Could you advice on it? I noticed that we can't migrate the form and report and query into SQL 2000. About the Oracle, there is a form and report tools. I have not idea whether it can be direct port over into Oracle.
Kindly adivce.
Thanks for the information but I need more implementatio/migration information on how to do it.
ht055,
Sorry, I'm afraid I'm not the best person to ask to judge between Oracle and SQL Server 2000, I've personally used neither.
However, that PDF file I linked does provide enough of an overview to the basic terminology you'll need when moving to a remote server, as well as the basic concepts.
I did do a quick google search (Oracle SQL Server 2000 comparison) and found a series of articles you might find useful at:
(Sorry for the ugly URL, but this site doesn't seem to support anything analagous to an A HREF tag and it didn't like the left-brace. So you'll have to use the Clipboard to get to those articles. Again, sorry.)
You'll need to register for the site, but it may have some of the information you're looking for.
Hope this helps...
-- Lance
Sorry, I'm afraid I'm not the best person to ask to judge between Oracle and SQL Server 2000, I've personally used neither.
However, that PDF file I linked does provide enough of an overview to the basic terminology you'll need when moving to a remote server, as well as the basic concepts.
I did do a quick google search (Oracle SQL Server 2000 comparison) and found a series of articles you might find useful at:
Code:
[URL unfurl="true"]http://www.informit.com/isapi/n~{2BB4CEB5-0A51-42FB-AABC-EC72C90BE6EF}/articles/index.asp[/URL](Sorry for the ugly URL, but this site doesn't seem to support anything analagous to an A HREF tag and it didn't like the left-brace. So you'll have to use the Clipboard to get to those articles. Again, sorry.)
You'll need to register for the site, but it may have some of the information you're looking for.
Hope this helps...
-- Lance
- Thread starter
- #5
Ah, the 64 million dollars question… Well, when all said and done, that's about how much it would cost you. ;-)
The answer is depends. It's like you have outgrown your VW bug, which is a better car, a Volvo Outback or a Ford F350? Again, depends. What are your cargo and how much money you want to spend?
The only thing you can move is the data. Even that, I would hesitate to move directly into either database. More about that later.
What hardware and software do you have? What hardware/software are available for use with the new database? Do you have the human resources, such as DBA, programmers/developers? How much time do you have to implement it? What do you want the database to do for you? How about the politics in your company? Pro-/Anti- Microsoft/Oracle. Regardless which one you choose, it will not be cheap. Last but not least, do you want to contribute to Bill Gate's $40+ million still-in-progress-beta-901.14-build-4087 mansion or Larry's $20 million sailboat? Unfortunately, there many questions/issues you much address first.
Back to the data. Getting the data into SQL or Oracle is relatively easy compare to others issues. I would redesign application to take advantage the strength of the new database. Also, a good chance to create an application that works well with the database and any future needs.
I would recommend reading the white papers on Microsoft and Oracle web sites. Also visit other site like this one to learn more about the strengths and weaknesses of each product and see if they are something you can live with.
Sorry, no quick and easy answer. Since no 2 companies are alike, you will have to do some homework and figure which one is more appropriate for your company.
Remember this, if you don't have the resources to do it right the first time, you are not going to have the resources to redo it later.
The answer is depends. It's like you have outgrown your VW bug, which is a better car, a Volvo Outback or a Ford F350? Again, depends. What are your cargo and how much money you want to spend?
The only thing you can move is the data. Even that, I would hesitate to move directly into either database. More about that later.
What hardware and software do you have? What hardware/software are available for use with the new database? Do you have the human resources, such as DBA, programmers/developers? How much time do you have to implement it? What do you want the database to do for you? How about the politics in your company? Pro-/Anti- Microsoft/Oracle. Regardless which one you choose, it will not be cheap. Last but not least, do you want to contribute to Bill Gate's $40+ million still-in-progress-beta-901.14-build-4087 mansion or Larry's $20 million sailboat? Unfortunately, there many questions/issues you much address first.
Back to the data. Getting the data into SQL or Oracle is relatively easy compare to others issues. I would redesign application to take advantage the strength of the new database. Also, a good chance to create an application that works well with the database and any future needs.
I would recommend reading the white papers on Microsoft and Oracle web sites. Also visit other site like this one to learn more about the strengths and weaknesses of each product and see if they are something you can live with.
Sorry, no quick and easy answer. Since no 2 companies are alike, you will have to do some homework and figure which one is more appropriate for your company.
Remember this, if you don't have the resources to do it right the first time, you are not going to have the resources to redo it later.
- Status
Similar threads
- Locked
- Helpful tip
- Locked
- Question