Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 Import/Export (DTS) and Replication (2000)
 converting foxpro 3.0 to sql server 2000

Author  Topic 

Mitnick
Starting Member

3 Posts

Posted - 2004-05-04 : 04:44:21
Hi,

I have thousands of foxpro 3.0 tables in a directory, with subdirectories.

I want to convert all of these tables to sql server 2000. The problem is that i have to convert them all thousand manually. Is there a posibility that i can set a directory with tables and convert them automatically into sql server 2000?

pjn
Starting Member

27 Posts

Posted - 2004-05-04 : 07:52:24
Do you also have a copy of Visual FoxPro? If so, there is an upsizing wizard that will do this for you. It's not perfect, but gets the job done.
Go to Top of Page

Mitnick
Starting Member

3 Posts

Posted - 2004-05-04 : 07:57:01
quote:
Originally posted by pjn

Do you also have a copy of Visual FoxPro? If so, there is an upsizing wizard that will do this for you. It's not perfect, but gets the job done.




I've got visual foxpro 8 as well. but the problem is that i only can open the tables. So i've got about 1400 directories with 10 tables that i have to open seperatly. or can you select 1 directory by the upsizing wizard? i can't see the option
Go to Top of Page

MichaelP
Jedi Yak

2489 Posts

Posted - 2004-05-04 : 14:42:43
Might I reccomend creating a new database in SQL Server? I've found that FP databases are generally very denormalized, so you might be better served by a total redesign. Simply upsizing thousands of tables will probably not gain you anything performance wise.

What is the goal of moving to SQL Server? Maintanability? Scalability? Performance?

Michael

<Yoda>Use the Search page you must. Find the answer you will.</Yoda>
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2004-05-04 : 15:47:59
quote:
Originally posted by MichaelP

Might I reccomend creating a new database in SQL Server? I've found that FP databases are generally very denormalized, so you might be better served by a total redesign. Simply upsizing thousands of tables will probably not gain you anything performance wise.

What is the goal of moving to SQL Server? Maintanability? Scalability? Performance?

Michael

<Yoda>Use the Search page you must. Find the answer you will.</Yoda>



I agree, whether you plan to redesign or not...data issues will become a concern...

Create a staging database based on whatever type sql server thinks they are...

Then analyze the data...

You can use DTS to transport the data...it's meant for this kind of thing...

Just don't try and do it all in 1 package...


Brett

8-)
Go to Top of Page

Mitnick
Starting Member

3 Posts

Posted - 2004-05-05 : 02:09:15
quote:
Originally posted by MichaelP

Might I reccomend creating a new database in SQL Server? I've found that FP databases are generally very denormalized, so you might be better served by a total redesign. Simply upsizing thousands of tables will probably not gain you anything performance wise.

What is the goal of moving to SQL Server? Maintanability? Scalability? Performance?

Michael

<Yoda>Use the Search page you must. Find the answer you will.</Yoda>



I have made a total new database in SQL server. But the data which is in the tables have to be converted into the new database so that's why.

i found a tool called MS SQL Import. with this i can convert more then 1 table at the time. so there is improvement! :)
Go to Top of Page

MichaelP
Jedi Yak

2489 Posts

Posted - 2004-05-05 : 12:56:05
If you are importing data, you might want to look at DTS. It should be able to handle importing LOTS of stuff.

Michael

<Yoda>Use the Search page you must. Find the answer you will.</Yoda>
Go to Top of Page
   

- Advertisement -