Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
Mikaell
Starting Member
1 Post |
Posted - 2009-11-24 : 07:36:31
|
Hi!We have setup what BOL describes as a "Standard Deployment" of Reporting Services 2008. That is the RS DB's on one server and and the Web (Reporting Services Server) on a second server.This has worked well until we discovered what we think is a bug with the excel rendering of reports, which crashes during export.After having searched for several hours we found some forums which pointed out that the SQL Server 2008 SP1 CU4 update would eventually fix it. The problem is that we aren't sure that our RS instance is being upgraded? First of all, it wouldn't find the RS instance on the "web server" unless we installed the SQL Engine first!? Then it would find the RS instance, and upgraded it.However Management Studio still says build 10.00.1600 !?!?! That's the RTM build? The DLL versions that we've checked says SP1, and the web (//server/reports) says 10.00.2734 (SP1 + CU4)Both SQL Engines and Analysis on server 1 is successfully reporting the SP1+CU4 build (10.00.2734)So my questions are:What version are we running?(I just can't understand how the RTM build can be reported, the other ones I understand)What is the correct way of applying Service Packs and Patches to a "Standard Deployment"?(We can't apply either of the service packs on server1, since there isn't an RS instance on it, though it holds both RS DB's)The whole point of splitting the DB and Web is to gain performance by saving resources for each instance (Mem, CPU, I/O's etc). Why do you have to install SQL Server on the RS Web instance so that the Service pack can find it!?BOL doesn't really cover this topic, or what a "Standard Deployment" actually is, and what Services that are included on each machine.Any help or clarification is much appreciated! |
|
|
|
|