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..
