Clever Geek Handbook

C # Sql server per client

I want to create an application that needs sql database on every machine using the application.

Isn't it true that Chrome and Firefox store cookies in a SQL database? I don't remember to install anything like SQL Server when installing Chrome, so my question is, should each user install SQL Server if my application uses one?

+3


source to share


3 answers


Best for your purpose is to use database servers that will run with your application, such as SQLite or Sql Server Compact. This means that you are using the database host and you have access to ADO.Net. This is a very smart way of storing local data and very simple.

Don't try to install complex database systems such as mssql, sybase, or mysql on every client.



For example, SQLite may ship with multiple assemblies in your product.

This answer gives a good overview: Lightweight SQL Database that doesn't require installation

+6


source


To store information for the client application, you can use SQL Server Compact or another solution such as SQLite (a library to access it).



There are other alternatives, but these two are the most common and stable.

+5


source


It is true that Firefox stores cookies in the sqlite database. However, this is not the same as SQL Server.

If your application needs to interact with a database, you can: a) bind a sqlite database to it, b) require an existing database to exist at startup (Wordpress does this: you can pass its information to the mysql database to get it use an existing one installation) or c) link a complete database (such as SQL Server Compact) to your application.

+2


source






More articles:


All Articles