Report Authoring - SSRS


Report Builder

Report Builder is a report authoring environment for business users who prefer to work in the Microsoft Office environment. Report Builder is a free download from Microsoft that can be installed on a Windows client or on the database server. For more details read the Microsoft documentation on the MSDN library.

Microsoft Visual Studio

Report authoring can only be done in the version of Visual Studio that supports your specific SQL Server installation. In fact, when you install SQL Server, you get an install of Visual Studio along with that. So, SQL 2008 installs a shell of VS 2005; SQL2008R2 installs a shell of Visual Studio 2008; SQL 2012 installs a shell of VS 2010; and SQL 2014 installs a shell of VS 2012. In general, the SQL version is one revision ahead of the VS version you use and the version of VS you get is specifically limited to report authoring. If you have a full compatible version of Visual Studio you can use your own copy but it's usually a good thing to use the version of VS that comes with SQL. 

Report Dataset Creation (Creating Stored Procedures)

  1. The dataset(s) required for any report must be created using SQL Server stored procedures. Stored procedures are required as MinistryPlatform requires any report to have three input parameters (Domain GUID, the User GUID and the Page ID). The Domain GUID can be found in the System Setup, and your User GUID is in your account. In general, we make these parameters for the stored procedure underlying the report so you can use it to check security, restrictions, limit data, etc. The Page ID is the actual numerical ID of the page you are launching. The Platform passes the parameters to the stored procedure. The stored procedures need only be declared. When creating your own stored procedures, it is best to assign a prefix to easily identify custom stored procedures from those created by ThinkMinistry.
  2. Input Parameter Details
    • @DomainID varchar(40)
    • @UserID varchar(40)
    • @PageID INT  
  3. Stored Procedure Example