Options for a file system based Sql database for a multiuser web application that can perform and scale [closed]

Question

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.

Closed 9 years ago.

What are my options for a file based sql database (not NoSql) which scales well, performs well, and is designed for handling many hundreds of multiple users (and plays nice with .net)?

My requirements

I'm accustomed to working with SqlServer, and for this application my needs are simpler (I still need sql though, although other parts of the application will use NoSql).

I want something which is embedded mainly because it's just simple and easy to set up, without any major overheads or services or configurations. I'd like to keep it filesystem for as long as I can.

However, when the time comes, ideally I'd like a solution which allows me to change the "context"of the database so maybe it is server based. I'd like that option to grow.

I'd also like it to be free (at least for small application, or non-commercial applications (although it will become commercial in the future...?)).

Does such a database solution exist?

Update

Sorry guys, I used the wrong terminology and ugh ink we misunderstood each other. Forget I said embedded, I meant file base, like lucene or raven, but relational.

Answer 1

You can use FireBird, it can be embedded and scales well and deployment is really easy - an ADO.NET provider is available... see for more information http://www.firebirdsql.org/en/net-provider/

Answer 2

You ever heard of SQL Server? Like SQL Server EMBEDDED? No install ;)

Answer 3

You have contradictory requirements.

Small and embedded (no server) usually means SQL Server compact or SQLLite. But these are neither multi-user not network aware in practice. Especially whan you say "hundreds of multiple users"

So you have to decide what you want to do. A proper, scalable, web based app with correct architecture? Or a a cheap kludgely unworkable unmaintainable mess?

SQL Server Compact will scale up of course in future to normal SQL Server with minimum fuss. But I'd start with SQL Server properly now