views:

1771

answers:

2

I have used SQLite.NET many times. It always worked fine but I have a friend that is really pestering me that I should use instead SQL Server Compact so I stayed fully in Microsoft environment.

Now, I never worked with Compact, and he tells me it works fine for him, but seeing that .MDF extension gives me the creeps. No kidding. Last thing I want is my application relying on an Access database.

Since I have never really worked with it, I am asking if someone here knows it to vouche for it, and if someone can tell me the main differences between them, mostly speed, file size, reliability, and features. I know it is a lot to ask but I'd appreciate if someone could help me.

+2  A: 

One thing is that the SQL Server Compact can only have one process accessing the MDF at a time.

Joel Lucsy
One process or one thread? It is a single application accessing the file so I don't think it would be a problem.
Leahn Novash
I'm fairly certain its just a one process limitation. It requires exclusive access to the file. But I think multiple threads should be fine. I never tried myself.
Joel Lucsy
Just found this information at http://download.microsoft.com/download/e/8/8/e8859616-e95d-41fe-9f81-ff88388d772b/SQLServer%202008CompareComapctExpress.pdfIt seems it doesn't have views, triggers, or stored procedures. Of course, sqlite doesn't have stored procedures either, but it does the other two.
Joel Lucsy
+1  A: 

Access was MDB (I believe it's changed for recent versions) - SQL Server full version defaults to MDF.

I confess I decided though that compact was just too much hassle from the docs so went with SQLite.

eftpotrm