[Ahmedn1]

I need to build application with a database that can have more than a million records in each table
but I want to make the installation to be very simple for the clients so I don't want to use SQL server
But MS Access capabilities will not be suitable for this

So, any ideas how to deal with this database?

[Vishu Sukhdev]

Hi,
You can use MySQL

[DivideByZero]

I haven't worked with Oracle much, but I know a lot of people that would recommend it first for a situation you're in

[Ahmedn1]

I know MySQL and Oracle
but they both have the same problem
the user must have them installed before he can install my application

[janne_panne]

I know there are atleast two which I have some experience about and neither requires installation, just ship the DLL with rest of the project: SQLite and VistaDB. But I'm don't know how well they handle millions of records for each table. VistaDB has indexes so it might handle massive amounts of data well enough.

You can try them, just generate lots of test data. For example create a loop which uses NBuilder (http://nbuilder.org/) to generate the data and insert it into DB.

[batesy3k]

That NBuilder looks pretty sweet. Might have to give it a whirl. Only downfall is their background is quite eye-watering! Those swirls !

But back on topic: It's like saying: How long is a piece of string?

Each database have their own pros and cons against so it is quite hard to recommend a database...

This post has been edited by batesy3k: 01 July 2011 - 08:14 AM

[jackbkjack]

You can use My SQL.It is good for managing large data.

[eclipsed4utoo]

I'd probably suggest SQLite.

[Curtis Rutland]

DivideByZero, on 01 July 2011 - 08:04 AM, said:

I haven't worked with Oracle much, but I know a lot of people that would recommend it first for a situation you're in

Nobody would recommend oracle for a simple client install. Or MySQL for that matter. Use a compact DB that doesn't need any installation, like Sql Server CE, or SQLite. Sql CE is the first choice, because it's made by MS, so if you know SQL Server, SQL CE isn't that different.

[Jeff H]

How many tables since you say each table can have more than a million records?
Or how much data are you needing to store?

This post has been edited by Jeff H: 02 July 2011 - 04:05 AM

[Ahmedn1]

So you guys agreed that SQLlite and SQL CE don't need to be installed
right?

[Jeff H]

http://msdn.microsof...y/aa983326.aspx

I have never used or tried it but take a look at SqlMetal for using Linq to Sql with CE
http://geekswithblog...ql.compact.aspx

This post has been edited by Jeff H: 01 July 2011 - 01:04 PM

[eclipsed4utoo]

Ahmedn1, on 01 July 2011 - 03:43 PM, said:

So you guys agreed that SQLlite and SQL CE don't need to be installed
right?

That is correct. SQLite and SQLCE do not need to be installed. The databases can be packaged with the application so it doesn't require anything from the user.

[Curtis Rutland]

SQL CE is the best choice, simply because it's built into VS and EF. You can add one to your project like this:



After you add, it'll offer to create a typed DataSet or an EF Model for your DB. I'd suggest using Entity Framework for it's simplicity.

Then when you create a setup package, it should include the DLL for Sql CE with the project output, if it's not already GACed on the target system.

SQLite is probably the next best choice, because it's portable like SQL CE, but it's not built right into VS. Also, I don't know if they have an EF provider for it.

Pretty much all your other options include a client-side DB install.