>>>>Hi,
>>>>
>>>>I have a feature in my app, scheduling procedure, where when user changes the schedule, the old records in a table have to be deleted and new added. In VFP version I was always "recycling" the records, that is "mark" them as "deleted" and then use them when new records have to be added. I am refactoring this procedure for SQL Server and consider doing away with "recycling". That is, delete records and let SQL Server "deal" with it. We are talking about deleting from 10 to 500 records (at the most) during the procedure. Should I still recycle in SQL Server or do away with this approach?
>>>>TIA
>>>
>>>It's outside your control. MS SQL has not RECALL.
>>>
>>>MartinaJ
>>
>>I know; I was not using RECALL (in VFP). I am setting a certain field value to 'D' and then look for these records (with 'D') and set the value back to empty. So my recycling (in VFP) is not Delete/Recall. So I could, in theory, apply it to SQL Server. But I am trying to simplify my code; hence this question.
>>Thank you.
>
>I you don't delete record you can rewrite algoritm for MS SQL.
>But it is good way? I don't know.
>What is ratio for "deleted" records and all records?
>
>MartinaJ
>
>PS: simply code= less bugs

I agree with your PS; this is the reason I am asking. The ratio is about 10% (I am guessing). Keep in mind that the entire table would have a max of 100,000 records/rows.