>>>Moving data from VFP database to SQL Server database is only the first step of the conversion. I have created a simple “to-do” list of what I should do to the data now that it is in the SQL Server. And I am wondering if you have any suggestions on what is missing in my list:
>>>
>>>1. For each table in the DB set Foreign Key Referential Constraints.
>>>2. Set Cascading Referential Integrity for updates in the primary table to be cascaded to the foreign key tables
>>>3. Create index tags on “key” fields.
>>>4. Create stored procedures that will be used to retrieve data for each application form and report.
>>>
>>>Anything is missing? TIA.
>>
>>Creating PKs first for EACH table :-)
>
>Good suggestion. When I converted tables to SQL Server I added to each table an identity column. And I think of it as the surrogate PK field of the table. Each table also has a what I called in VFP a candidate field for which a user creates an entry (e.g. "CUSTOMER_ID"). When you are saying PK you mean the identity column or the candidate field (unique) that user enters?


Each table has to have Primary key.
The identity column is good for this (it is a little harder to manage it from the FrontEnd than uniqueidentifier (GIUD)).
But ALL referential integrity of the DB should be done via that Primary key.
All queries from your front end should have that PK in mind :o)
Usually (not necessary) PKs have nothing related to the information in the table. They just didn't hold any information about the record (like RECNO() in VFP).
That is because that way you easier could change the valuable information w/o need to change the related table.