RATE THIS ANSWER
-1
Click to Vote:
0- -1
What to prepare if we are going to migrate instead.... or what are the steps that we should take. Thanks.
correcting and adding my posted question.
-------------------------
I have several Btrieve databases being pulled into SQL 2005 via SSIS.
Basically you will need to create a connection into the database (ODBC is best here in my experience) and build an SSIS package to pull in the tables (and their contents) into tables in SQL.
You will of course have to write the queries to oull the data in, either the complete contents of the tables, or of course limiting what columns/rows are pulled through. This is obviously a god time to do some house keeping if you need to.
You can either design these tables in SQL yourself or let the server do the work for you (i prefer the former) and have the data imported.
You haven't said at all though what you are going to do with your data once it's in SQL..... is it static (data warehouse) or will it be used with an application? This will have a bearing on how you need to import your data i.e. will it be a regular import, or a one off? how will the application migrate if at all? What security requirements will you need to implement in sql?
Data migration, Database migration, Migration, Pervasive, SQL Server migration, SQL Server 2005
Hi! could somebody help us advice on what to do and what to prepare if we are going to migration our current database Betrieve tables to MS SQL Server 2005? Thanks.
