How Do I Properly Deploy One SQL Server Instance Tied To Winforms Application On Multiple Clients?

Question

0.00/5 (No votes)

See more:

I am a student working on a pet project to improve on win forms, c# and MSSQL.

The idea for the application is for an instance of SQL Server Express to be hosted on a Windows Server 2008 machine with clients installing the application on their machines and being able to update the database hosted on the server using it.

Now, I've worked on it on my machine thus far using VS 2008 and SQL Express, it works fine and would now like to deploy the database on the server. But I lack the experience to do so as previous projects I've worked on in the past had local DB copies bundles with the install file.

Now what remains is to;
a)Create/transfer the locally stored instance of the SQL Server(Express) from my local machine to the server.

b)Give client machines the ability to access the db via the recommended connection i.e LAN or remote connection using the windows forms application I have built.

Can someone please give pointers on how to achieve this or give links to articles which adequately cover the subject matter?

Thanks in advance.

Posted 6-Oct-14 10:00am

zillaitor

Add a Solution

Comments

Sergey Alexandrovich Kryukov 6-Oct-14 16:02pm

How a SQL server can be tied to "Winforms Application"? This is your application which can be "tied" to the server.
—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2014-10-06T10:09:00

Well, deployment of SQL Server or SQL Server Express is possible. You can even embed SQL Server Express in your application:
http://social.technet.microsoft.com/wiki/contents/articles/940.how-to-embed-sql-server-express-in-an-application.aspx[^],
http://technet.microsoft.com/en-us/library/bb264562%28v=sql.90%29.aspx[^],
http://msdn.microsoft.com/en-us/library/aa983326%28v=vs.90%29.aspx[^].

However, in most cases, more viable solution would be just claiming a database server product, or a set of compatible products of certain compatible versions, as the prerequisite. It can suite more users. Some users can have their own license for some compatible commercial version. They would probably (and reasonably) prefer reusing it, instead of adding some redundant software.

—SA