using databases with vb.net applications

what's the best way?

[mattglet]

a fellow programmer of mine is producing a client application using vb.net to store some records. he obviously needs to use some sort of a database to do this. he was going to use xml, but he said that it uses too much ram? he's using disconnected datasets in the application to output the records to the screen. this means all the record outputs get stored in memory. his app then becomes overly bloated. the app would probably hold about 10000 records or so. would access be a better database solution?

i am having a hard time believing that he is properly creating this app. should he be using disconnected datasets? is there a proper way to (hopefully an online tutorial) that shows how to do this? thanks for your help.

-Matt

[aspdaddy]

It depends on what you are doing and what performance you are after.

Disconnected recordsets can be useful because they give you all the functionality - sort, query, update etc that arrays dont have - saves you writing a custom container class if you are already familiar with ADO.

One thing I would question is the lost update problem, transaction integrity etc. as disconnected recordsets may corrupt the master data if you have several concurrent users.

[korkus2000]

Access could work but it would be so much easier with SQLServer. MSDE is the new free version of SQL Server that is real nice. You have to own a license of SQL Server Enterprise or VS.Net Architect I think to be able to distribute it. It is made for client apps.

The disconnected dataset should be ok if it is a client app. Makes me wonder how big the data structure is. One thing is that datareaders can boost performance if you are not manipulating the data.

[mattglet]

unfortunately, MSDE is not an option right now, because of the cost. it is probably going to be available in a future rewrite of the app, after some revenue has been generated.

a few points to the statements you have both made:
-there will be no concurrent users to the app. the app is geared towards a single person keeping track of records.

-new records will be added/updated frequently

the thing that made be bring up this question in the first place was because the app was using 11mb of RAM upon opening it, and then jumped to 23mb after retrieving about 100 records (about 15 fields per record, with XML) using the disconnected dataset. does that sound right?

-Matt

[plumsauce]

Actually, Microsoft is a bit more generous than that.

To wit:

Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) is a free, redistributable version of SQL Server 2000 that can now be downloaded from the SQL Server website. The MSDE 2000 download provides users with the right to install and use MSDE with your applications or development projects. You must register for the right to redistribute MSDE with your applications

So, either get your users to download themselves, or
register to include it with your stuff.

MSDE is also a part of MS OFFICE, which your users
may already have.

+++