Is there a development environment for Reporting Services (2005) that is integrated with source control?
You can use Visual Studio to develop reports and place them under source control. But as far as I can tell, you cannot implement security, scheduling, etc. through Visual Studio. For these you can use a second environment, e.g. SQL Server Management Studio - but is this environment integrated with TFS?
In other words, is there a single development environment, integrated with TFS, where you can develop all aspects of Reporting Services reports?
I wouldn't get all excited about using SQL Server Management Studio for that second set of tasks, since they have pretty much indicated that they would prefer to concentrate on making Report Manager and Sharepoint the tools for this purpose in Katmai. I think the Management Studio snap-in approach didn't give them the flexibility they wanted, it's kind of rigid.
Please read below, from Brian Welcker's Weblog (http://blogs.msdn.com/bwelcker/ ) --
Meanwhile, remember that all the details you are actually configuring through either approach are actually in a database... So you do have ways of versioning them by taking snapshots of data.
I don't mean to make light of your concerns, and source control isn't directly integrated with the report management data that's in the database. As far as I know, it's aimed at scripting work (you can read this http://msdn2.microsoft.com/en-us/library/ms173550.aspx for information) .
But the data itself can be backed up on a regular, versioned basis and you can probably check the whole .BAK file into your source control repository if you want to (I don't know what you'd gain, but ReportServer DB's are metadata, they aren't going to be huge). If you created scripts for this purpose, you would of course have the integrated ability to version the scripts.
HTH -- see below for the Katmai information I was referring to...
>L<
(snip) - (http://blogs.msdn.com/bwelcker/ )
Watusi (SSRS Management Tools Changes for Katmai)
For Katmai we are considering the removal of namespace management (folders,
reports, data sources, models) from the Reporting Services Add-in for SQL
Server Management Studio (SSMS). In other words, we are considering removing
the 'Home' folder under the Reporting Server node in SSMS.Why the change?
Customer feedback and usage data indicates that Report Manager and/or
SharePoint are the tools of choice for managing the Report Server namespace,
rather than the SSMS add-in. The design constraints of SSMS mean that any
new namespace functionality is significantly expensive to implement,
specifically adding support for the namespace in SharePoint integrated mode.
For Katmai we want to invest in SharePoint and Report Manager for namespace
management and focus on SSMS as a server-level management tool.This means that the namespace management functions that are not available in
Report Manager (Model ClickThrough and Model Item Security) will be added to
Report Manager (they are already in SharePoint). Job Management, configuring
System properties, and administering Roles will be moved to SSMS. In
addition, SSMS will be updated to work in SharePoint mode.If you have feedback about these changes, please feel free to comment.
No comments:
Post a Comment