<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
I have an application in VB6 that is being migrated from dBAse IV to SQL Server 2008 R2 database. &nbsp;There are several 'documents' that are organized into a header table and detail table where the detail table has multiple records. &nbsp;<br />
<br />
When the 'document' is edited, &nbsp;some of the rows from the detail could have been deleted, some added, or some just changed.<br />
<br />
What is the best practice for doing this type of work?<br />
<br />
1 - update each record based on the record's unique key and then delete any record that isn't in the document anymore?<br />
<br />
2 - delete all records and re-insert only the rows in the document?<br />
<br />
Thanks for your input!
</div>
</div>


Hi,

I have an application in VB6 that is being migrated from dBAse IV to SQL Server 2008 R2 database.  There are several 'documents' that are organized into a header table and detail table where the detail table has multiple records.  

When the 'document' is edited,  some of the rows from the detail could have been deleted, some added, or some just changed.

What is the best practice for doing this type of work?

1 - update each record based on the record's unique key and then delete any record that isn't in the document anymore?

2 - delete all records and re-insert only the rows in the document?

Thanks for your input!

What is the best SQL server practice for editing a document that affects multiple tables/rows?

Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the  Always On technologies and support for unstructured data types.

Microsoft SQL Server 2008

Visual Basic is Microsoft’s event-driven programming language and integrated development environment (IDE) for its Component Object Model (COM) programming model. It is relatively easy to learn and use because of its graphical development features and BASIC heritage. It has been replaced with VB.NET, and is very similar to VBA (Visual Basic for Applications), the programming language for the Microsoft Office product line.