In the never-ending search for design/compile-time checking of object dependencies I would like to request that database references be introduced into SSRS.
Database references were introduced into Visual Studio database projects in Visual Studio 2005 Service Release 1 (http://blogs.msdn.com/b/gertd/archive/2007/07/26/database-references.aspx). They are very useful because they enable you to reference database objects that don't exist in the current project and hence provide compile-time checking that stored procedures .
I see no reason why the same construct shouldn't be introduced into SSRS/SSIS/SSAS. Each of those technologies reference objects in a database - why shouldn't we have compile-time checking to ensure that the referenced objects actually exist.
1) If a SSRS report pulls data from a view, I want to know that that view exists. Similarly, if the view definition changes I want to know that my report will still work.
2) Similarly for a SSAS cube, if the a view referenced in the DSV changes or disappears I want my SSAS project build to fail accordingly
3) Similarly for a SSIS Execute SQL Task, if it executes a stored procedure I want to know that that stored procedure has the correct parameters.