title: SQL Server Table and Column Alias for legacy applications
body: <p>Having just started working for a new client  I have noticed that their database schema could do with a serious overhaul.  I've made some suggestions (naming conventions mainly) which would be acceptable for the new suite of applications we are developing going forward, however the system would also have to support the lagacy names used (i.e. 400 or so externally hosted web applications). </p>
  
  <p>Is there any way I could do the following:</p>
  
  <ul>
  <li>Change the naming of tables and columns for use in the new application.</li>
  <li>Create a permanenet table alias or similar to allow the lagacy code to remain unchaged?</li>
  </ul>
  
  <p>Bit of a long shot.......</p>