Sqlite uma boa escolha para C #?[fechado]

Question

seria uma boa escolha para uso dentro de um serviço wcf escrito em c #?Eu estou usando o Firebirdsql, mas isso está me dando muitos problemas.Documentação e suporte também é horrível.

Editar: Desculpe, eu deveria ter sido mais específico ao fazer a pergunta.O que eu quis dizer foi se o sqlite é uma boa escolha para um banco de dados incorporado dentro de C #.O SQL está fora de questão para este.

Answer 1

SQLite is a great platform for any language, however there are small concerns I've had with it under .NET.

1. It is natively compiled. This breaks .NET's AnyCPU Implementations of .NET (i.e. you have to explicitly distribute a 32bit & 64bit version of your app, and have some hand-written rules in your .csproj (MSBUILD) file to select the different dependencies based on what you select.
2. It has some sticky threading issues. You're going to run into trouble if you're trying to use the same DB from multiple places (multiple instances of your app) etc. It's doable, but it basically uses a simplistic form of database/table locking to achieve this, which could be a major concern based on your program.

All In all i really like SQLite, but if I could find one that didn't require a redistributable (*cough*SQL Express*cough*), I would use another embedded DBMS for .NET Apps. To date I havent found one aside from Raven DB but that's a document DB.

Edit: Note, Raven DB Is also only free for open-source applications. It's not suitable for proprietary applications unless you're willing to shell out for a licence, so when looking into it please be sure to factor it into your budget.

Answer 2

SQL Express always works well