Blog from the Microsoft SQL Server product team.
This morning, Satya Nadella, President of Server and Tools Business group, announced during his keynote the public availability of the CTP3 of Microsoft SQL Server Code Name “Denali”.
One of the key scenarios for Microsoft SQL Server Code Name “Denali” is the continuation of our self Service BI story which we introduced in SQL Server 2008 R2 with the introduction of PowerPivot for Excel and SharePoint.
If you haven’t had a chance to attend or view it live, I recommend you review Satya’s keynote: http://sessions.digitalwpc.com/topic/list?keyword=VIS03
With Microsoft SQL Server Code Name “Denali”, we are proud to announce the availability of Self Service Alerting and Self Service Reporting (Project Crescent).
Self Service Alerting:
Alerting is a new capability that we are adding to Reporting Services. As soon as the report server is upgraded to Microsoft SQL Server Code Name “Denali”, it will enable any user that can access reports previously built with SSRS 2005, SSRS 2008 or SSRS 2008 R2 whether in Report Builder or BIDS, to setup alert rules and be alerted when report data changes occur that match a set of rules. No changes are required to the existing reports. You’ll need to have SSRS integrated with SharePoint in order to take advantage of this new capability (the reports must also use stored credentials data sources, similar to subscriptions). Management of alerts is also enabled through SharePoint through a common interface.
Project Crescent is not the final name of this capability, but is the current code name used to refer to the new Self Service Reporting capability.
Project Crescent is part of Reporting Services toolset and is an extension to the existing IT Professional and Power User tools.
Project Crescent is Reporting Services’ new reporting tool targeted at data consumers to visually explore their data and answer ad-hoc questions with ease. It complements our existing set of at IT Professionals, BI Developers and power users Report design tools (Report Builder 3.0 and BIDS), which are optimized for operational and pixel perfect report design scenarios.
Project Crescent is replacing Report Builder 1.0, which had been our initial entry in the Adhoc reporting space back in SQL Server 2005. Report Builder 1.0 shall subsequently stop shipping in the box starting with Microsoft SQL Server Code Name “Denali” release.
Report Builder 3.0 is now renamed Report Builder. Report Designer is still the name of the report design experience available in BI development studio and Visual Studio.
Project Crescent is an ad-hoc reporting and visual exploration experience for casual and experienced users alike, to collaborate and present with others within a SharePoint environment.
Project Crescent runs in the browser and is working against a BI Semantic Model (BISM). BI Semantic Model is available on the client through the Excel based Power pivot modeling tool or on the server through Analysis Services Tabular project with SQL Server Denali. For more information on BI Semantic Model, please consult the Analysis Services team blog at: http://blogs.msdn.com/analysisservices
Unlike Report Builder 3.0 or BIDS, which are tools optimized for report printing and report design by Power users and IT pros to publish for End users to consume, Project Crescent is optimized for design and online screen consumption and interactivity by End users for End users…
But beyond Self Service Reporting (Crescent) and Self Service Alerting, SQL Server codename Denali has many more enhancements for our other Reporting scenarios….
The team has worked hard over the last 2 years to provide new benefits to customers in the area of Self-Service BI (with Crescent and Alerting), Corporate BI, Embedded BI and the new rising Cloud BI space:
How can you learn more about Crescent and SSRS in Microsoft SQL Server Code Name “Denali”?
Over the next 2 to 3 months we will make a lot of information available around Crescent (including sample models and reports), Self Service Alerting, Reporting SharePoint Share services and Office renderers so stay tuned….
If you have questions on Microsoft SQL Server Code Name “Denali” Reporting Services new features, you can find some answers and help at…
If you are encountering an issue, please follow the regular support channel as they full support and assist with issues in Microsoft SQL Server Code Name “Denali” CTP3.
For peer discussion and exchange of information, all discussion around Reporting Services in Denali should now be posted on our Reporting Services forums:
Or use your local Reporting Services forum if you are in a different geographical region and locale.
Call to action:
And do not hesitate to leave us a comment here in this blog. Be assured that it will be seen, responded to if needed and incorporated in our planning cycle for Reporting Services V.Next….
Enjoy this CTP...
Thierry D’Hers (Group Program Manager, SQL Server Reporting Services)
Dave, now that CTP3 is out, let's get working on the MS Mobile BI development we've been talking about. I'll email you. CTP3 has some really great functionality we can incorporate.
Project Crescent definitely looks exciting!
Will Cresent have the ability to deal with Left/Right outer joins by default other than by abstracting them to views which is highly IT centric, and defeats the object of an 'ad-hoc' reporting capability?