[RESOLVED] How to save data that changes frequently locally before it's saved in db at the end ?

[bluebarca]

I have a project for an attendance system where a local pc scans to see how is present every 30 minutes and updates the number of scans each individual person has passed up untill the end of the session; where i should read this data and save the final attendance in a SQL Server 2005 database based on who passed a certain amount of scans.

first i thought to make this temporary list a temp database table but this is inefficient on the large scale.

How should i save a list of dynamic data locally, and updating some values in it untill the final values are sent to be saved at the server ?


Is XML the way i should go or is there a better way to go ?


Thanks very much for the help;
bluebarca

[darwen]

first i thought to make this temporary list a temp database table but this is inefficient on the large scale.


Unless you're dealing with hundreds of thousands of users this won't be inefficient if you design your database tables correctly (with the appropriate indexes).

I'd go with storing the information in a central database.

Darwen.

[boudino]

You can use some embedded database, but XML doesn't appear to be the best way, I'd say.

[JonnyPoet]

I would use an offline Dataset, DataTables as this is easy to maintain and easy to store the changes and it will only store the changes. This alos enables you while storing to get informed when the original data have been changed from another Client in between ( if this could happen in your casescenario ) IMHO an efficient way to be used