Yeah, a template will make your reporting infinitely easier. If you want to get fancy schmancy, grab this: http://www.madisonusergroup.com/2012/11/28/octobernovember-2012-meeting-notes/
Routine and Code blatantly stolen from John Nelson (with permission); let's you have really pretty reports, using your company's logos and colors.
I start w/the Template based on that for everything, and don't think Report Builder 3.0 is any worse than the .ASP reports. Of course... I'm geeky enough that I build my queries first in Sql Management Studio first anyway... then open RB3.0; the template, Save As New Report, and paste in the query I've already vetted outside of Report Builder.
From: Daniel Ratliff <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Tuesday, August 20, 2013 8:56 AM
Subject: RE: [mssms] SCCM2012 Reports
The information transmitted is intended only for the person or entity to which it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information in error,
please contact the sender and delete or destroy the material/information.
Routine and Code blatantly stolen from John Nelson (with permission); let's you have really pretty reports, using your company's logos and colors.
I start w/the Template based on that for everything, and don't think Report Builder 3.0 is any worse than the .ASP reports. Of course... I'm geeky enough that I build my queries first in Sql Management Studio first anyway... then open RB3.0; the template, Save As New Report, and paste in the query I've already vetted outside of Report Builder.
Sherry Kissinger
From: Daniel Ratliff <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Tuesday, August 20, 2013 8:56 AM
Subject: RE: [mssms] SCCM2012 Reports
Yeah but that was maybe an hour, once, when you first setup. Then you could churn out reports in 15 minutes flat.
Now it takes an hour just to do a single report in SSRS with all the design required. I haven’t tried Jason’s ‘save as’ trick to make a template though. Hope to test that
later this week.
Daniel Ratliff
From: [email protected] [mailto:[email protected]]
On Behalf Of [email protected]
Sent: Tuesday, August 20, 2013 9:50 AM
To: [email protected]
Subject: RE: [mssms] SCCM2012 Reports
Sent: Tuesday, August 20, 2013 9:50 AM
To: [email protected]
Subject: RE: [mssms] SCCM2012 Reports
I don’t miss it at all. Any idea how many times I had to fight with time outs, too many rows returned and hacking IIS to make it work?
From:
[email protected]
[mailto:[email protected]]
On Behalf Of Todd Hemsell
Sent: Tuesday, August 20, 2013 7:17 AM
To: [email protected]
Subject: Re: [mssms] SCCM2012 Reports
Sent: Tuesday, August 20, 2013 7:17 AM
To: [email protected]
Subject: Re: [mssms] SCCM2012 Reports
I miss the old reporting. Management likes the new reporting. It is prettier.
Old one was VERY easy to make a new report and publish it. Also very easy to go in and edit it.
I might look around for a simple web app that executes SQL and returns it in a table..
On Mon, Aug 19, 2013 at 8:45 AM, Trevor Sullivan <[email protected]> wrote:
Greg,I agree overall with your analysis. It’s not an ideal solution, but personally I prefer to simply run SQL queries inside of SQL Management Studio (SSMS). It’s the easiest way for me to obtain raw data when necessary. Unfortunately, this doesn’t help for publishing information to end users.From: [email protected] [mailto:[email protected]] On Behalf Of Greg DeGuire
Sent: Friday, August 16, 2013 10:53 AM
To: '[email protected]'
Subject: [mssms] SCCM2012 ReportsIs there any way to create a simple report the ‘old school’ way (2007)?By this I mean just entering SQL, typing all the joins, etc. and getting a report quickly – like the ‘grey bar’ reports from 2007?It just seems to me like ANY report in 2012 is a lot of needless clicking/width adjusting for even the simplest output…
The information transmitted is intended only for the person or entity to which it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information in error,
please contact the sender and delete or destroy the material/information.

