title: Better way to manage Database class for common operations
body: <p>Our company work on multiple <strong>Windows Services</strong> and <strong>EXEs</strong> (more than 30). Each of the service/exe have one database class which have connection details and respective SQL queries.</p>
  
  <p>Now, whenever some change come, our team need to maintain all the projects, which takes a lot of programmer's time and efforts. Also seems inappropriate.</p>
  
  <p>I was wondering if there was a better architecture to manage such kind of structure. So that it can save programmer's time and repetitive effort.</p>
  
  <blockquote>
    <p>What I have think is that to maintain a common DLL, which will have
    all the connection detail and SQL queries. Maintaining this structure
    using inheritance will save a lot of repetitive effort.</p>
  </blockquote>
  
  <p>Is there any better way to manage this? What are your opinions?</p>