April 21, 2017 at 10:34 am
Dear all,
I would like to know if I can run SSRS16 on a mirrored MSSQL 2016 server.
I am going to upgrade from MSSQL 2005 to 2016 and would like to have 2 separate mssql instances in order not to affect performance while running SSRS reports.
Is this a good solution.
Thanks
Giovanni
April 21, 2017 at 4:07 pm
Sue
April 23, 2017 at 11:01 pm
Sue_H - Friday, April 21, 2017 4:07 PMThank you very much Sue,
I really appreciate your advice,
GiovanniYou probably don't want to think about mirroring for that upgrade since it is going away - the replacement being always on availability groups.
In terms of staying with mirroring - no it won't work with SSRS. The biggest issue being that only user databases can be mirrored.
If your main concern is just with reporting interfering with other activities on a database server, you could install SSRS on it's own server. It doesn't need to be on the same server as other user databases. If it's used heavily, you'd probably want to use two servers - one for the databases and the other for the Services.
If availability is a concern, going to always on availability groups in 2016 would be better than mirroring. The requirements, issues, behaviors in this environment are documented in this Microsoft article:
Reporting Services with Always On Availability Groups (SQL Server)Sue
April 24, 2017 at 1:40 am
Sue_H - Friday, April 21, 2017 4:07 PMSue ,
In order to run SSRS reports with Always on configuration do I need MSSQL 2016 enterprise edition ? I do only have Standard Edition.
Thanks
GiovanniYou probably don't want to think about mirroring for that upgrade since it is going away - the replacement being always on availability groups.
In terms of staying with mirroring - no it won't work with SSRS. The biggest issue being that only user databases can be mirrored.
If your main concern is just with reporting interfering with other activities on a database server, you could install SSRS on it's own server. It doesn't need to be on the same server as other user databases. If it's used heavily, you'd probably want to use two servers - one for the databases and the other for the Services.
If availability is a concern, going to always on availability groups in 2016 would be better than mirroring. The requirements, issues, behaviors in this environment are documented in this Microsoft article:
Reporting Services with Always On Availability Groups (SQL Server)Sue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply