avanderlaan
Programmer
- Jul 11, 2002
- 156
I am looking for recommendations on the best way to convert a large ACCESS db (> 1 million rows) to an industrial strength relational engine (DB2 or SQL Server 2000). The front end is already VB. Cutover can be done when the lab facility is not working (weekend), so one-time performance may not be such a major concern.
Sometime during the conversion I will be normalizing and splitting tables, converting to ANSI data types and switching from char to integer keys. I was planning to do the conversion in 2 steps: 1) move the data into SQL, and 2) schema/key modifications. For the sake of discussion, let's assume that the relational engine will be SQL Server 2000. I was considering writing a DTS Data Driven Query Task to automate this migration. Is this reasonable? Are there ACCESS functions that I can use to export/push the data into SQL Server? What have I missed in my cursory analysis?
While I have 10+ years of experience with embedded SQL and DB2 and Oracle, I have never used an ACCESS db. :~/
Thanx.
Sometime during the conversion I will be normalizing and splitting tables, converting to ANSI data types and switching from char to integer keys. I was planning to do the conversion in 2 steps: 1) move the data into SQL, and 2) schema/key modifications. For the sake of discussion, let's assume that the relational engine will be SQL Server 2000. I was considering writing a DTS Data Driven Query Task to automate this migration. Is this reasonable? Are there ACCESS functions that I can use to export/push the data into SQL Server? What have I missed in my cursory analysis?
While I have 10+ years of experience with embedded SQL and DB2 and Oracle, I have never used an ACCESS db. :~/
Thanx.