It worked btw: SQL reporting and reporting point on an external box. Cool.
From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Mittwoch, 18. September 2013 12:25 To: [email protected] Subject: RE: [mssms] CM12, Reporting Point on remote box Well, I have another reason to move reporting: I do expect heavy use of automation, so I want to have another sms provider (I also do that for the two primaries, but use the remote SQL box for that). Now, with the CAS and SQL on the same server, there is no server left. I'd rather not just move SQL because of the provider, hence let's move reporting to another and use that one also as an sms provider. I get two things at the same time: a possible bottleneck resolved and the workload spread on the smsprov. Back to topc. Not sure I want to use another instance. It seems that moving the workload really happens when SSRS is installed on the remote box and also the role is there. Putting SSRS on the DB-server looks like only a partial solution. Not sure worth it then. So, CAS, SQL (CM-DB) on one. SSRS, reporting DB and the reporting role on the other. That does work as I understood it. -R From: [email protected] [mailto:[email protected]] On Behalf Of Craig Andrew (OIZ) Sent: Mittwoch, 18. September 2013 10:50 To: [email protected] Subject: AW: [mssms] CM12, Reporting Point on remote box I recently installed a SMSProv and CM DB on the same server then installed the reporting DB on a separate instance on this same server, with the SSRS instance and the reportng services point on a separate server. This was due to customer requirements, and their SQL standards. The SSRS instance aside, does it make sense to have the Reporting DB for the SSRS on the same server as the CM DB? Separate instance on same server? Separate server? Does it impact performance? I havent seen any performance issues but i need to scale this model if possible. Not sure I entirely understand the SSRS, it needs it's own DB but does it use it or does the SSRS instance grab data direct from CM DB? Thanks Andy Von: [email protected] [mailto:[email protected] <mailto:[email protected]> um.com] Im Auftrag von Roland Janus Gesendet: Mittwoch, 18. September 2013 01:33 An: [email protected] Betreff: RE: [mssms] CM12, Reporting Point on remote box Hi Steve, that is about the number of clients we have today for CM12. What made you do this, I guess also the possible load? There is no bottleneck yet, there is nothing installed for CM12, which what this is about, but I'd like to avoid one if there is one. Not sure I go through the effort, nevertheless, good to know. Thanks, Roland From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Dienstag, 17. September 2013 16:27 To: [email protected] Subject: RE: [mssms] CM12, Reporting Point on remote box Hi Roland, You can have a dedicated remote Reporting Point. We do that here for our 140K clients. You'd need to install SQL Server RS on that device and enable it as an RP. No CM data needs to "move" there, connection strings enabled the reports to use data wherever the CM SQL is located. You may or may not see a performance improvement on your CAS/Primary. The load placed by SSRS is fairly small. you may want to spend some time understanding where your SQL bottleneck(s) is located. At the very least baseline your current performance, offload RS and measure the difference. Steve From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Monday, September 16, 2013 10:02 AM To: [email protected] Subject: [mssms] CM12, Reporting Point on remote box I'd like to remove the load from reporting from the CAS or primary. Does it make sense to put a reporting point on a remote box? Remote to SQL? Have SQL reporting installed on SQL, but the RP role on a remote box? How about having a dedicated SQL/Reporting Server just for reporting? Then of course the data has to get there somehow from the site server SQL box. Any ideas? It does sound like not supported though..
