Solved

WIndow form accessing a SQL Server on network

Posted on 2011-02-17
5
783 Views
Last Modified: 2012-06-21
Currently we have a C# .net windows application that uses a local desktop instance of SQL Server.  We wanted to know the challenges of changing this model to using a single instance of a SQL Server on a network.

First, I am assuming it is not a problem for a desktop windows form application to access a SQL server on a internal network given the connection parameters are provided.  Please correct me if I am wrong.  What other things do we need to consider if we decide to make this change?
0
Comment
Question by:Hojoformo
5 Comments
 
LVL 9

Accepted Solution

by:
rawinnlnx9 earned 250 total points
ID: 34920858
This is a larger topic than you are aware of. Mainly you need to configure your connection strings to use an SQL server by name or IP on the network.

This is from my config file, yours should be in app.config. You need to use a connection string that has been configured to use that server.

<add name="SiteSqlServer" connectionString="Data Source=WEBDEV\SQL2005;Initial Catalog=LAB;User ID=sa;Password=1234pass" providerName="System.Data.SqlClient"/>

Open in new window


Then from your code you'd set your connection string to:

ConfigurationManager.ConnectionStrings["SiteSqlServer"].ConnectionString;

Open in new window


0
 
LVL 52

Assisted Solution

by:Carl Tawn
Carl Tawn earned 125 total points
ID: 34920870
There shouldn't be anything major. Just make sure that the firewalls on the server and the clients will allow traffic through on port 1433, and that incoming connections are enabled on the SQL Server (they should be by default if it is a full-blown sql rather than express, but it is something to bare in mind).

Obviously you need to make sure that the server has enough processor, RAM and disk resources available, but i assume you have already done that.
0
 
LVL 29

Assisted Solution

by:anarki_jimbel
anarki_jimbel earned 125 total points
ID: 34920940
Some challenge may be finding DB server on a network but it shouldn't be a big problem

Connection string - it's obvious. And may be it's better to use Windows authentication on an internal network... Anyway, shouldn't be a big problem...
0
 
LVL 11

Expert Comment

by:Sudhakar Pulivarthi
ID: 34922306
0
 
LVL 2

Expert Comment

by:KentMarsh
ID: 34929632
Classic "Client Server".
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Introduction Hi all and welcome to my first article on Experts Exchange. A while ago, someone asked me if i could do some tutorials on object oriented programming. I decided to do them on C#. Now you may ask me, why's that? Well, one of the re…
This article is for Object-Oriented Programming (OOP) beginners. An Interface contains declarations of events, indexers, methods and/or properties. Any class which implements the Interface should provide the concrete implementation for each Inter…
In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now