Ideas to Update DATA received from the client
-
I have not big DB (12 tables) Suppose application is requested for some data about specified clientID by means of ADO.NET i got all the relevant data about this clientID from several tables to the client, client perform tasks on this data change it maybe add something new or delete somtething (there is posibility that data will not changed at all), after this client click to SAVE button and return data to DB, here start the problem, i can delete all relevant data about specified clientID in all table and after this insert data tables (insert data that recieved from the application) or i can check what changed and to remove or update or insert data. ANY IDEAS, and maybe how to perform my problem. I'm using: Windows Xp, .NET Framework, Sql-Server 2000. ------------------------------------ To study, study and only to study
-
I have not big DB (12 tables) Suppose application is requested for some data about specified clientID by means of ADO.NET i got all the relevant data about this clientID from several tables to the client, client perform tasks on this data change it maybe add something new or delete somtething (there is posibility that data will not changed at all), after this client click to SAVE button and return data to DB, here start the problem, i can delete all relevant data about specified clientID in all table and after this insert data tables (insert data that recieved from the application) or i can check what changed and to remove or update or insert data. ANY IDEAS, and maybe how to perform my problem. I'm using: Windows Xp, .NET Framework, Sql-Server 2000. ------------------------------------ To study, study and only to study
To delete all relevant data and insert them again will be taxing to your database server. For best performance you can balance between tables to be deleted (best for one-to-many relationship such as multiple selection) and tables to be updated (best for one-to-one relationship e.g. a table with many columns). If you are using datasets, specify all the insert, delete and update commands and let it do the work for you. Edbert
-
To delete all relevant data and insert them again will be taxing to your database server. For best performance you can balance between tables to be deleted (best for one-to-many relationship such as multiple selection) and tables to be updated (best for one-to-one relationship e.g. a table with many columns). If you are using datasets, specify all the insert, delete and update commands and let it do the work for you. Edbert
However if i don'et use dataset, i'm developing only db i don't care what hapen in the application layer. What i should do do delete relevant rows and insert after this or to do some manipulation with data to understand what chenged and aafter this to insert o to delete or to update some rows???? ------------------------------------ To study, study and only to study