>>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?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
