How can I connect to sql database from another machine?

Question

0.00/5 (No votes)

See more:

I have a c# application with sql server 2008 database in windows authentication mode. when i run it in my system it works well.
But when i share c# app in network, I can not connect to database and i get error( a network related or instance...).
this is my connection string:

C#

conn = new SqlConnection(@"Server=localhost;Database=OfficialAutomation;Integrated Security=true;");

What should i do?
Thanks in advanced.

Posted 19-May-13 23:29pm

MJ MOUSAVI

Add a Solution

2 solutions

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)

Johnny J. · Answer 1 · 2013-05-19T23:31:00

Solution 1

Try replacing "localhost" with the IP address of the machine:

C#

conn = new SqlConnection(@"Server=XXX.XXX.XXX.XXX;Database=OfficialAutomation;Integrated Security=true;");

I assume that the user that is logged in can access the machine on the network?

Otherwise, you might want to switch to SQL Server authentication...

Posted 19-May-13 23:31pm

Johnny J.

Updated 19-May-13 23:34pm

v5

Comments

MJ MOUSAVI 20-May-13 8:21am

I change server name to ip address but i didn,t get any answer.
then i switch to sql server authentication and enter with sa.
but in other machine again i,v got error.

Johnny J. 20-May-13 8:32am

Sounds like a network problem. Can you ping the address of the the DB server machine?

MJ MOUSAVI 20-May-13 8:53am

yes, when i ping the address,i get answer.

OriginalGriff · Answer 2 · 2013-05-19T23:38:00

Server=localhost says that the SQL instance is located on the current PC - which it isn't, it is located on your development machine (which is why it worked when you wrote it). There are two things you can do about this:
1) Change the connection string to refer to the absolute address of your developemnt machine. This is relatively trivial:
Set up a connection in VS with the Server Explorer pane:
1.1) Open Server Explorer.
1.2) Right click "Data connections" and select "Add connection"
1.3) In the dialog that follows, select your DataSource, and database, specify the security info, and press the "Test connection" button.
1.4) When the connection works, press "OK"
1.5) Highlight your database in the Server Explorer pane, and look at the Properties pane. A working example of the connection string will be shown, which you can copy and paste into your app or config file. This will be absolute "pc/instance" rather than "localhost" related.
Or
2) Set up a second machine as an SQL server for production, and use the absolute address of that instance instead.

Personally, I would use the second - that way when you continue work on the application, you will not accidentally affect the production database. Image the mess you could make if you forget to add the WHERE clause to an UPDATE or DELETE statement!

BTW: You should also take the time to move your connection string from a hardcoded value as you show in the question to a configuration file (of some description) based setting, so that you can switch your PC between production and development SQL instances without changing the software - it makes it more reliable, and helps to ensure that when you upgrade their software, the users don't switch back to the development server and mess everything up! :laugh: