Einar,

Thanks for the reply.

To clarify... I might have one record in a product table that is for a guitar and then there is a related 'variant' table that holds the sku number, color, etc for each modification of that guitar.

If that one guitar changes I was going to delete the one record in the product table and possibly 10 records out of the variant table (for example) and then readd the one guitar and 10 variants. The other non-related records would not be deleted and readded.

So what do you think now? Do you think this is acceptable?

Thanks
Paul

>Paul,
>If a record in a table in a database on M$ SQL Server is deleted it is deleted and not like VFP where it is marked for deletion and you have to pack the table to remove it completely.
>
>Just to see if I understand you, you are deleting all the records from the table and then you are adding all the records back in with just one new/modified record compared to the table before you deleted all the records? If that is the case I would investigate redesigning it so that you don't have to do all that work (or rather make the SQL server do all that work).
>
>Anywho just my $0.02
>
>Einar
>
>>I am using SQL Server for the first time with C#. I have a webservice that manages a products table in SQL Server. This webservice accepts XML and either adds product or updates product. For reasons I won't go into here, for each update I am needing to delete the product record and all related records in other tables and then readd the udpated item in the product table and related tables.
>>
>>Long story short, this webservice is going to be deleting a lot of records in SQL Server. Are they still there marked for deletion like in VFP. If so, how do I remove them?
>>
>>Should I rethink this method of deleting records and re adding for all updates?
>>
>>Thanks for your input and suggestions.
>>
>>Paul