leop1212
asked on
SQL 2008 R2 STD Installation problem
I have SQL 2008 R2 standard installed on Windows 2008 R2 server.
I do need to install SSRS . When I add SSRS it shoes me Web Addition is installed. getting S . I’ve downloaded fresh ISO of SQL 2008 R2 standard not WEB and removed SSRS and run 2008 R2 setup and when install SSRS still indicate that it is Web addion.
.
How can I install SSRS standard instead of WEB without destroying my SQL server instance as I have few important DB running.
I would appreciate the answer from someone who has experience with this type of problem without wild guessing.
I do need to install SSRS . When I add SSRS it shoes me Web Addition is installed. getting S . I’ve downloaded fresh ISO of SQL 2008 R2 standard not WEB and removed SSRS and run 2008 R2 setup and when install SSRS still indicate that it is Web addion.
.
How can I install SSRS standard instead of WEB without destroying my SQL server instance as I have few important DB running.
I would appreciate the answer from someone who has experience with this type of problem without wild guessing.
ASKER
Christian,
I do have to have SSRS installed on the same box as this is required by my ERP
and I do need is to replace SSRS web with SSRS standard without preferbly without reinstalling sQL
I do have to have SSRS installed on the same box as this is required by my ERP
and I do need is to replace SSRS web with SSRS standard without preferbly without reinstalling sQL
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi,
Some parts of SQL are installed as an instance - SQL/SSRS/SSAS, and others aren't SSMS/BDS/Browser
I suggest that so long as resources are okay on this server, you look at installing another instance of SQL and another instance of SSRS.
Although I haven't done so with SSRS, and only done it with SQL, it is easy to mix editions & versions of SQL as different instances.
ie my last production build had SQL 2008 R2 Standard 64 bit (two instances), SQL 2008 R2 Standard, SQL 2008 R2 Developer 64 bit.
HTH
David
Some parts of SQL are installed as an instance - SQL/SSRS/SSAS, and others aren't SSMS/BDS/Browser
I suggest that so long as resources are okay on this server, you look at installing another instance of SQL and another instance of SSRS.
Although I haven't done so with SSRS, and only done it with SQL, it is easy to mix editions & versions of SQL as different instances.
ie my last production build had SQL 2008 R2 Standard 64 bit (two instances), SQL 2008 R2 Standard, SQL 2008 R2 Developer 64 bit.
HTH
David
ASKER
that did it.
maintenance /version upgrade it just like that!
thank you very much
maintenance /version upgrade it just like that!
thank you very much
it's some years ago since I've installed a SSRS. Correct me if I'm wrong but as far as I know the Reporting Services can only be run through a web interface. So if you install a Reporting Services Server you must specify which Web Service you use so the Reporting Services can be installed there or otherwise let the installer install a Web Service (IIS by default) for you and configure it.
The Reporting Services are independent of your SQL Server Database Service so this installation would not change anything in your normal SQL Server. To be more exact, it is strongly recommended to not install the Reporting Services and especially the Web Service on the same machine as your normal database. The workload would be separated to different hardware services and the Web Service should be on a third machine to also make the network more secure. A Web Service could always be target to a hacking attack so if it is hacked you have not necessarily opened your database or report server.
For the installation there is no general way of installing it because there are a lot of possibilities how to install it. You should read the installation guidelines from Microsoft very carefully and decide how to install it in your case. I personally would install database, report and web server on three different machines, separated by different hardware (or VM solutions). The Reporting Service and also the Web Service should get separated domain accounts which are only used to run these services with exact settings about the rights. This needs a lot of extra tests since it is able to run anything but almost better than allow a standard system or network account to run them. Depending on your network you need to run a lot of tests and manual configuration but the security is almost better. It's your decision.
The installation guidelines ("Considerations for Installing Reporting Services"):
http://msdn.microsoft.com/en-us/library/ms143736%28v=sql.105%29.aspx
(where you can amongst others see a "file only installation").
and this one ("Planning and Architecture (Reporting Services)"):
http://msdn.microsoft.com/en-us/library/bb522679%28v=sql.105%29.aspx
Your very best friend will be this tool after installation ("Reporting Services Configuration Tool"):
http://msdn.microsoft.com/en-us/library/ms156305%28v=sql.105%29.aspx
Cheers,
Christian