By Garth Jones
With the upcoming release of SQL Server 2016, I thought that I would get a head start by testing SQL Server 2016 Release Candidate (RC) 0. In particular, I wanted to test SQL Server Reporting Services (SSRS) with System Center Configuration Manager (ConfigMgr).
I know what you’re thinking. SQL Server 2016 isn’t even released, so it’s very unlikely that ConfigMgr will support it!
You might be asking yourself at this point why I would think SQL Server 2016 RC 0 SSRS will work with ConfigMgr. Well, I did a fair amount of research on both SSRS and Power BI, and the future of both. If you read my earlier post about Power BI, you will know that both SSRS and Power BI are slowly becoming one product. SQL Server 2016 is the first step towards that goal.
According to a number of webcasts, the SSRS portion of SQL Server 2016 was re-written to help handle mobile reporting and Power BI, but how does everything work with ConfigMgr?
I was anxious to get started, so I performed a few tests on two SSRS sites attached to a Central Administration Site (CAS).
While performing the tests, I laughed to myself because I could hear Brian Mason @abetterpc saying, “Why do you want two SSRS sites attached to your CAS? Nobody does that!” I would answer Brian by saying, “I have actually seen it done. Heck back in the SMS 2003 days, with ASP reporting, I would set this up all the time,” but I digress.
Now, let’s focus on getting SQL Server 2016 setup as a ConfigMgr reporting point.
The setup for SQL Server 2016 is almost exactly the same as SQL Server 2014. By the way, there’s a new tab that I noticed in the set-up Wizard. It looks interesting because it deals with temp db settings. I’ll look into that in more detail at some point in the near future.
In the ConfigMgr console, since there already was an existing reporting point, I setup this reporting point on the new SQL Server 2016. Installing the reporting point on SQL Server 2016 is very similar to any other version of SQL Server/SSRS.
When I got to the Specify Reporting Services settings page (see screenshot below), I must admit that I was unsure if this would work or not. Once I saw the SSRS SQL instance (red arrow) listed within the Wizard page, however, I had high hopes that this first test of SQL Server 2016 would work for ConfigMgr reporting!
Next, I verified the database and setup the execution account before completing the setup.
My hopes grew even more when the setup completed successfully.
I then moved over to the SQL Server 2016 server where I found the srsrpsetup.log and then confirmed that the install was successful (green arrow). I was really starting to get excited that everything was going to work correctly!
Wow, everything does work correctly!
How does it look in the new SSRS interface? See the screenshot below.
The report looks the same to me. Now I can run my tests with two ConfigMgr reporting points attached to my CAS! I’m truly impressed and will be writing a lot of posts about SQL 2016, SSRS and Power BI! Keep an eye out for this over the coming months.