I am currently writing the SQL code by hand in Management studio then importing that code into Report builder data sets. It works well and you can create some very rich reports. The big downside to report builder is not the code you have to write, it is how tedious it is to make things look good. If you care about the look and feel of your reports you are going to spend a very long time editing all those properties and whatnot.
For organizing reports I create a folder that I place all my custom reports in and then to give access to the non SCCM users I assign rights to ad user groups and then just give them the direct link to the report so that they do not try to browse around. --------------- Scott Keiffer Senior Systems Administrator Cockrell School of Engineering - IT Group University of Texas at Austin skeif...@austin.utexas.edu 512-814-8872 From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Trevor Sullivan Sent: Thursday, October 31, 2013 8:48 AM To: mssms@lists.myitforum.com Subject: [mssms] Feedback Request: Developing ConfigMgr 2012 Reports Hey folks, I was just hoping to gather some general feedback about how people are developing and publishing ConfigMgr 2012 reports. Now that we no longer have classic ASP reports, how are you writing reports? Are you using SQL Server Management Studio (SSMS), Report Builder, or Business Intelligence Development Studio (BIDS)? What tools have you found easy (or hard) to use, and what is your workflow for creating reports, and publishing them out to business end-users? Do you create Active Directory security groups to restrict business users to specific SQL Server Reporting Services (SSRS) folders? How do you organize your folders? Any additional feedback you can provide would be helpful, including screenshots. Cheers, Trevor Sullivan
smime.p7s
Description: S/MIME cryptographic signature
