Home/ Questions/Q 6812805
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T20:29:39+00:00

I have only been programming for the better part of 1-2 years, C# the

  • 0

I have only been programming for the better part of 1-2 years, C# the last 7 months or so, Up til now I have used the .config file to store needed settings that cannot be stored in the database, and it was okay to do so.

Now I have a client where there are many users that will access a database, and part of the spec is that the application must log into sql using the sa username, obviously if anyone gets hold these settings it would be a problem.

I want to know what the best practice for something like this would be, I can encrypt the password and server address, but I still feel uneasy about this.

What is the best practice in the industry for storing settings that cannot be in the database, especially the ones that are sensitive configurations

Many Thanks in advance

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can put settings into a local database. I prefer MS SQL Server Compact 3.5, which is free. This way you can store your settings into a local SDF database file, which can be encrypted and password protected. The data stored in the SDF file can be accessed using e.g. ADO.NET+SQL, but I prefer Linq-to-SQL.

    EDIT:

    Please take into account that although SDF files can be encrypted and password protected, if the file is stolen, it can definitely be cracked by a brute force method. The same is true for any other solution, which stores sensitive data on client machines.

    • 0