title: Possible effects of dynamically changing connection string from web.config file
body: <p>Recently I've been studying about rewriting/replacing ConnectionString from the Web.config file. Suppose I have a 'dummy' account in my original web.config here:</p>
  
  <pre><code>&lt;connectionStrings&gt;
      &lt;add name="OracleDBConnString" connectionString="Provider=MSDAORA;Data Source=ISDDEV;User ID=dummy_account;Password=password;"
        providerName="System.Data.OleDB" /&gt;
  &lt;/connectionStrings&gt;
  </code></pre>
  
  <p>Base on this post: <a href="https://stackoverflow.com/questions/360024/how-do-i-set-a-connection-string-config-programatically-in-net">How do I set a connection string config programatically in .net?</a>, I can change the connection string from web.config dynamically but are there any negative effects if I change the connection string dynamically during runtime? Are there any 'conflict' if I have multiple users (with different accounts or conn string) accessing the system? Do you have any suggestions on what approach I can use?</p>
  
  <p>The reason why I have to change the conn string is because I don't actually maintain passwords inside the database instead I use the login details of the user in the database directly. Thank you in advance.</p>