Solved

WIndow form accessing a SQL Server on network

Posted on 2011-02-17
5
786 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
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 30

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

Secure Your Active Directory - April 20, 2017

Active Directory plays a critical role in your company’s IT infrastructure and keeping it secure in today’s hacker-infested world is a must.
Microsoft published 300+ pages of guidance, but who has the time, money, and resources to implement? Register now to find an easier way.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Entity Framework is a powerful tool to help you interact with the DataBase but still doesn't help much when we have a Stored Procedure that returns more than one resultset. The solution takes some of out-of-the-box thinking; read on!
Performance in games development is paramount: every microsecond counts to be able to do everything in less than 33ms (aiming at 16ms). C# foreach statement is one of the worst performance killers, and here I explain why.
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

733 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