Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Which local database should be used for C# Windows applications?
I am very confused about Localdb, SQL Server Express and SQL Server Compact.
And install on client Machine.
SQL Server Express is the currently favored option by Microsoft. It's a full database engine, but it must be (separately) installed on the client's PC, and it starts up as a Windows service in the background.
SQL Server LocalDB is a developer-oriented special version of SQL Server Express, with the same feature set, and it, too, must be installed. Other than SQL Server Express, it doesn't start up as a Windows service in the background, but it gets fired up when your application starts, and terminates when your application finishes its work.
SQL Server Compact Edition is a very different beast - uses .sdf files, is a single-user, embedded database, meaning you just need to include a few *.dll in your project, no separate installation needed. It's limited in its features, and it's no longer developed any further by Microsoft and will eventually go away
If you absolutely must have a "no-install" approach, you'll need to investigate other options, like SQLite or others.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am new at programming and I want to make an app which uses a SQL Server database. Most important feature of this database must be usable for every computer which has the app installed.
I mean, when I give this app's setup file to another person, this person should be install my app without installing SQL Server program, extra things etc. I don't know it is possible.
I created a database with "SQL Server Object Explorer" inside of "(localdb)\MSSQLLocalDB" but when I tried to add new connection, server name was empty. So I didn't import a database to my project.
So how/where can I create and import a database ?
If you want a local SQL database with your application, that is: data is not shared between devices or users, you'll want something like SQLite which is designed for embedding in distributed applications.
To use it you need to link against the binary and include the binary in your application package. Or, you can use the SQLite team's native C# SQLite library. See here: https://system.data.sqlite.org/index.html/doc/trunk/www/index.wiki
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I create an application using C# and SQL Server database, when I try to create the setup I realized that I need to install SQL Server and create the database in every computer that I install my app on.
Is there any way or software can create the setup with the database without install the SQL server in other computers?
If your storing data locally you are better off to use SQLite (as Flat Eric mentioned, it needs no installation and it efficient on small DB's) then you can just copy the .mdf files instead of having to install the entire SQL server on every machine. Visual Studio provides great functionality to help you set up a LocalDB.
Here are two useful links, They really helped me in these situations:
Upgrade to LocalDB
Creating a Local Database File in Visual Studio
Connecting to Data in a Local Database File (Windows Forms)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am new to programming in windows environment with Visual Studio most of my work is done in web and PHP .I have to build windows application for a store and the store has to add stock/make bills and sort expired products and the stuff related to stuff so what database backend should i prefer?i thought of microsoft sql but i have to install it on clients system or any simple alternative would be more helpful ?
I asked a similar question here:
Local file-based SQL Server
I had used SQL Server previously, but like you, it had to go onto a client's computer. I'm now using "Microsoft SQL Server Compact Edition (CE)" as suggested in the answer, and this works really well as a standalone database solution.
For deployment point of view I suggest you to use MS Access Database. It is most flexible and simple in use also. Check following link for same
http://office.microsoft.com/en-in/access/
I am using MDB (access database), but for the next project thinking to go for SQLite.
Reason is because MDB access via OleDb is not working in 64 bit applications. You have to compile software as 32 bit, then it will work under 64 bit OS. Or other solution is to install something, called ADE, what will add provider, which solve the issue.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have created a Windows Forms application in .NET 4.0. Now there are about 20 client machines where the application has to be reinstalled every time there is a build change.
Is there a way I can push the application to all the machines in the client network in a single go?
ClickOnce is your friend.
In short, ClickOnce allows you to publish an application to a server and users can browse to an associated installation website and install your software.
If your ClickOnce settings are set properly, each time the user launches the application, the application will check for an update on the server, download it if it exists and update then application.
It's worth noting that with each update, the entire application is re-installed. This can save you a ton of headaches but if your application is large, it could be a nightmare for your users if you update the system frequently. Hit the link provided above for all of Microsoft's information regarding this deployment mechanism.
You can have your sysadmin create a Group Policy to do this.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I am planning on writing and commercialising a C# app which will store data in an underlying database
I use MySQL on my environment for my own development and this is what I would have used to write the application for myself (no need to use FK - MyISAM engine would be fine).
I am concerned about how easy it will be to distribute the app together with the database engine.
Would using MySQL allow me for easy packaging of the app for a "one-click" install on the client side? (ie I do not want them to have to install MySQL by themselves) and also is it feasible from a licensing point of view?
Are there other Database systems which would make the process more straight-forward
Take a look at SQL Server Compact 3.5
Sqlite is very simple. You just deploy the DLL with your app. I can't tell how appropriate it is for your situation, given the lack of info.
I think SQLite could do the trick, as it is a filesystem-based database, so no installation required.
Access could also do the trick, and most of businesses have it already installed as part of Microsoft Office, though you wouldn't need it to be installed in order to use the Odbc or OleDb assemblies that are part of the GAC.
The key here is what kind of database you need. Is this database to be shared among several users of the app? If so, than MySQL would be fine.
But it sounds more like you intend to use this database as a private data store, where each installed instance of the application has it's own data local to that machine or profile. In that case, you want an in-process engine like Sql Server Compact Edition, Sqlite, or even Access rather than a server-class engine like MySql or Sql Server Express Edition.
I think, that an embedded DBMS is the best way for yor. For example, you can use Firebird Embedded
SQL Server 2008 Express is available for redistribution by ISVs. You an also deploy this using Microsoft Web Platform Installer.
SQL Server Express is another option. Has excellent integration with .NET, free to install and supports upto 10GB per database (or more if you use the Filestream feature).