Of course, its difficult to say without additional info.

I'm also doing lots of such type of conversions. Some thoughts


- When you look at the taskmanager, is the VFP process CPU bound?
- Open the resource monitor, how is the disk I/O doing?
- Fragmentation of the SQL database, perhaps some indexes are added (or change of clustered index) ?
- Are the TABLEUPDATES() done in batchmode (multiple INSERTS/UPDATES in one SQLEXEC)? You can check in SQL profier
- If you are running a 32 bit version of SQL server, the fastest way is to insert records directly through using the VFP ODBC driver and using openrowset().
- Disable all triggers before the conversion
- Remove all non-clustered indexes before the conversion
- if you still have a regular HDD, GET AN SDD. It makes a world of a difference.

Walter,



>Hello all.
>
>Andy is on a VFP to .NET and SQL Server conversion project. He is using VFP to migrate the data into SQL Server. The process to push the VFP data into SQL Server used to take about 45 minutes and he has been running this code for over a year. All of a sudden, for no apparent reason, the process has come to a screeching halt and is taking over 12 hours to run. Andy did not change any of his code, so it has to be something else like a Windows update.
>
>Does anyone have any ideas?
>
>TIA.