CODEWITHSUNDEEP
c#.netsqllocal-database
PICyourBrain
PICyourBrain

Reputation: 10294

developing sql application using local database

I am starting an application (c#, .net) that will interact with a Microsoft SQL database. I need the ability for multiple clients to access the data concurrently so I an going to use a service based database (.mdf). Is it possible to develop the application using a local database (.sdf) and then easily switch it over to a service based database when it comes time for deployment? Is that how this type of development it typically done?

Upvotes: 1

Views: 1137

Answers (5)

Vroomfundel
Vroomfundel

Reputation: 732

If you have multiple clients then you should use SQL Server Express (.mdf file) - SQL Server Compact (.sdf file) is useful when you are building an application that is going to be deployed on client machines and will run standalone, e.g. windows forms application with a local database. SQL Server Compact is just an alternative for MS Access .mdb files or SQLite, the so called "embedded databases", while SQL Server Express is a real database server (albeit with some limitations to render it unsuitable for large commercial applications) and should be used in the cases where multiple clients use central database, e.g. web applications and smart client apps (the latter could also make use of a local embedded database though).

Upvotes: 0

Arie
Arie

Reputation: 5373

You want to use SQL Compact Edition (as you said database file extension is .sdf), right? You can use MSSQL Express Edition instead, as it acts more like full MSSQL Server, and is still free and not so hard to install on developer's machine (I personally prefer this option). There are differences between the two (as explained here: http://blog.sqlauthority.com/2009/04/22/sql-server-difference-between-sql-server-compact-edition-ce-and-sql-server-express-edition/). If you don't want features like triggers/procedures/views in your database, you can still use CE, though.

Upvotes: 0

JohnFx
JohnFx

Reputation: 34907

Development shops vary, but it is pretty common to develop apps using SQL Express locally and then use a full installation of SQL Server for the production environment.

The only thing I would advise is make sure that the DB you chose for your dev environment supports the same features as what you expect in production. For example don't use SQL Express on your dev box when you expect to use Oracle in production.

Upvotes: 1

Jakub Konecki
Jakub Konecki

Reputation: 46008

You can control the data source by providing connection string to your database in .config file.

You can even create Debug and Release versions of your .config file with different connection strings. Debug can point to your local machine and Release to production.

Upvotes: 1

Petar Petkov
Petar Petkov

Reputation: 1479

If the database schema in both backends is exactly the same than the only thing you will need to do is change the connection string when you are ready to move to the service based database. Be aware that the slightest change in the schema can (and probably will) cause problems.

Upvotes: 0

Related Questions