[SSRS] Declare database object dependencies - by Jamie Thomson

Status : 


Sign in
to vote
ID 597707 Comments
Status Active Workarounds
Type Suggestion Repros 0
Opened 9/14/2010 3:43:00 AM
Access Restriction Public


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.

For example:
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.
Sign in to post a comment.
Posted by Jamie Thomson on 12/7/2010 at 1:51 AM
Database references are confirmed as coming to Juneau (https://connect.microsoft.com/VisualStudio/feedback/details/602252/entity-fx-use-database-references-to-constrain-the-edm?wa=wsignin1.0). How about adding them to SSIS/SSAS/SSRS as well?
Posted by Microsoft on 11/18/2010 at 3:08 PM
Thanks for sharing your feedback. This is a great suggestion. I've added it to our list to consider for a future release.

Bob Meyers
SQL Server Reporting Services