How to create remote settings file?

Question

0.00/5 (No votes)

See more:

I have one windows form based application which has SQL Database.

SERVER Machine Has(Windows PC):Application & Database File & SQL Server
Client Machine Has:Only Application

Server Does:allows Remote connection to sql server
client Does:use application & connect with server database or sql server

i wants to create setting file & it will be used through network to connect sql sever via remote connection with TCP/IP

settings like sql server name,database file name,username password etc.

I know this can be done using:
1) Store setting file in server machine & share via netwrok
2) Newtwork Registry

which option is better for me & which is more reliable?

What I have tried:

currently i am trying to conncet to sql server via tcp/ip manually writing sever name & etc but i need setting file like server name database name etc.

I am installing application in each client and this application will conncet to server database which is stored in server machine.

Please Suggest one option.

Posted 12-Sep-17 18:05pm

Hardevsinh Mori

Updated 12-Sep-17 18:29pm

Add a Solution

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)

Wendelius · Accepted Answer · 2017-09-12T18:29:00

Solution 1

I'm not sure that storing a setting file with username and password on the network is a good idea. In overall you should avoid hard coded, shared user accounts in a client server environment.

If you store the password in a file, even encrypted, you need to be able to decrypt it in order to use it. Basically this means that anyone who has access to the file can also figure out the password

When connecting to SQL Server you have two options:
- If you use SQL Server authentication, you can ask the user name and the password from the end user.
- Preferably use Windows authentication so that the AD takes care of the actual user identification.

Posted 12-Sep-17 18:29pm

Wendelius

Comments

[no name] 13-Sep-17 0:53am

hello sir
i want this file for sql conncetion string so if i change file i will reflect to all machines apllication conncetion string

Wendelius 13-Sep-17 0:57am

As far as I can see the easiest way would be to put the server name and the instance and the database name to a file in a network share. You can use whatever format you like, personally I'd use XML because it's easy to read and serialize/deserialize.

However, my point is, do not store the whole connection string in this file. Leave out the username and the password.

[no name] 13-Sep-17 1:08am

ok. Thank You. I accept your Solution.