title: porting over database changes to SQL Server Reporting Services to avoid breaking reports
body: <p>When database changes are made (tables and column names renamed or eliminated), my shop struggles with broke reports which we react to after deployment. There is no established practice to fix the reports to reflect the changes before going live with the database changes.  </p>
  
  <p>I have the databases set up as SQL Server database projects in VS and have them committed to GIT. The reporting services files (<code>.rdl</code> files) are in GIT as well. Googled everywhere to see if a database project can be connected to no avail.</p>
  
  <p>Whenever a database object is changed (renamed a column for example) in a database project, I am looking for an efficient way to fix the references to the renamed column in the SQL Server Reporting Services project.</p>