Quick question... Is all data in SQL-Server...???

Also, you scenario sounds backwards. Typically, production/transaction databases update data warehouses...not the other way around... Please clarify this...

IAC, if you need the power of VFP Cursors, then I would suggest using SPT and stored procedures to actually perform the updates....


>I'm sure this debate has been held before, but I'd like to lay out a scenario I have and solicit input from anyone having gone through this.
>
>I have a SQL Server database in place used daily by up to 50 clients on a LAN. I have a data warehouse currently maintained by a VFP 6 application with data that needs to be merged into the existing SQL database. The data warehouse collects data from many different sources and periodically we need to refresh the production SQL database with information collected and stored in the data warehouse.
>
>The existing data warehouse can be moved to SQL server if we need to and if it makes sense. It contains around 250,000 records, likewise the production SQL database contains around 250,000 records. Both will grow at a very slow and steady growth, maybe 10 - 20,000 records a year.
>
>Which method would you use to update data in the production database from the data warehouse, Remote Views or SQL Pass through? I'm leaning towards remote views because it is a more familiar way of working with the database, but since there are no controls to bind data to (it's all just programmatically checking each record in the data warehouse, if it exists in production update the production record, if it doesn't exist, insert it into the production database). Any thoughts?