sql server doubt

Drupan

scenario : There are 10 computers on LAN and one system will have MS SQL installed on it.. now my doubt is how will the application route the information into the database .. in the application i have hard coded the sqlserver name.. is this enough? and a good practice.. or are there any other requirements to send the data from the application to database??

5 Replies

Know the answer? Post it — somebody with the same question will find it here.

Pankaj Gupta17y ago
You can store the connection infomation in the config file and acess it in the application through config and it is configurable without any effect on the application. :)
J18y ago
The ideal scenario is to place all of your data access code in one place (on the server) and have clients connect to it through a serialized interface (i.e. web services or remoting interface)
Kirtan Patel18y ago
Store your Connection String parameters in Application Setting or External XML file
So that if your server is changed you can easily modify the client application to work with those changes without modifying the client application programming .
it will give your client application portability to work with any server in LAN :)

Happy Coding :)
Rohit K18y ago
As far as the best practice is concerned, the connection string is not hard coded in the application. It is stored externally (encrypted in critical scenarios) so that you can modify easily in production environment.
Vijaya Kadiyala18y ago
Hi

When you are providing connection string that will have server information and database which you want to access.

ex:

Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;

As long as you are in Network it will work.

Thanks -- Vj

http://dotnetvj.blogspot.com

http://oravj.blogspot.com