Determine if SQL connection is local or remote

Question

0.00/5 (No votes)

See more:

I am trying to develop an application that runs sql scripts either or on a local or on a remote sql server to update values on the application. The connection status is checked using:

TcpClient client = new TcpClient(serverName, 1433);

Once we know that we can listen using the port, I will have to pass the login credentials to the SQL server either using Windows/SQL server authentication. But the problem is that the application needs to determine if the server it is connecting to is local or remote based on which the functionality of the application can vary.
e.g: Use integrated security if using local windows authentication.

Can anyone please assist me in as to how I would be able to determine if the connection is remote or local as based on this my application can be developed to enable different functionality/properties.

Thank you.

Posted 30-Jan-13 6:24am

Member 9557085

Add a Solution

Comments

PIEBALDconsult 30-Jan-13 13:11pm

Why would you not be using the ADO.net classes?

Member 9557085 30-Jan-13 13:58pm

The connection to the databases are made using the ADO.net classes where I am providing the connection settings. I tried using the ADO.net classes to rectify this problem as well but with no success. If you think its possible to achieve this using ADO.net classes please do let me know. Thanks..

PIEBALDconsult 30-Jan-13 14:30pm

Then what is the problem? If it's database-related then ADO.net should work.

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)

Dave Kreskowiak · Answer 1 · 2013-01-30T06:45:00

You wouldn't normally do this. At install time, you'd ask the person installing the app for the name of the SQL Server and instance, port number, and credentials to use, giving them the option of using Windows Authentication. You'd then construct the connection string from that information and test the connection if required.