A new blog about SQL Server Reporting Services

I thought I’d start off my new blog with a quick welcome and introduction. My name is Riccardo Muti and I work at Microsoft as a Program Manager on the SQL Server Reporting Services team. My area of focus is the rendering engine and various rendering extensions – everything about the way your reports render, whether in the previewers in our report design tools (Report Builder, Business Intelligence Development Studio), in our web applications (Report Manager, SharePoint), in other applications (via our ReportViewer controls), in your Outlook inbox, or exported to various formats (Word, Excel, PDF, and more).

I hope to use this blog to share important concepts and useful techniques, tips and tricks, news updates, and other content that I hope you’ll find valuable. I welcome your feedback – about either this blog or the product – so feel free to rate posts, leave comments, or send me your thoughts.

I’ll leave you for now with some valuable resources:

• SQL Server Reporting Services Developer Center on MSDN.
• Books Onlineon MSDN. Particularly,
  • Report Design Tips
  • Exporting Reports
  • Page Layout and Rendering
  • Troubleshooting Reports: Report Rendering
  • Troubleshooting Reports: Reports Exported to a Specific File Format
• SQL Server Reporting Services Product Samples on CodePlex.
• SQL Server Reporting Services Team Blog and other blogs.
• SQL Server Reporting Services Forum on MSDN Forums. A great place to ask questions and receive answers from Microsoft and the community.
• SQL Server Connect on Microsoft Connect. The place to report bugs and submit suggestions to Microsoft.
• Microsoft Support. Where to go if you need to open a support case with Microsoft.

Thanks for using SQL Server Reporting Services!

-Riccardo

[The usual disclaimers: The opinions and views expressed in this blog are those of the author and do not necessarily state or reflect those of Microsoft. This blog is governed by the MSDN Terms of Use . Contents are licensed under the Creative Commons Attribution-NonCommercial-NoDerivs license .]