We have an older application using VFP tables. We have a website that's been migrated from VFP tables to SQL Server. Before when we pushed/pulled data we would just Secure FTP it the local drive and then import it into app.



The tables have anywhere from 400-30,000 records, about 20 fields. We we're thinking of using ES to handle the transfer, over a fast connection. It involves clearing the server tables, and then creaing new records in BO with VFP data, and when done, save all the records to server. With the given scenario would that be something within the capabilities of ES?



Also, to add one more variable to the mix, the SQL Server tables are more normalized than the VFP tables. So new keys have to be generated for the SQL server tables, and there are some parent child relationships. In this case would it be better to just use GUID's for those fields (I've read up on them in the forum already), so that it will avoid a round trip to the server to get the AutoIncrement values, or would AutoInc's not be much of an issue because of the size of the tables? We're trying to minimize the length of time this takes so it can be completed within about 15 minutes (at the most no more than 30, but quicker is better )



Thanks,



Marcel



P.S. - Is it common practice to use GUID's as ForeignKeys or do they usually only use GUID's for the parent tables and all child tables contain INT keys? INT's might cause issues for me, so that's why I'm asking.