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.
Who is Participating?
BitsqueezerConnect With a Mentor Commented:

maybe there are some new things in SQL Server 2008 (I work mainly with 2005), but I don't know anything about two different versions of SSRS. As I said above, SSRS cannot run without a web application server because you can only access a report with a browser. I don't think that's different in 2008 and I could not found anything about a "web edition" or "standard edition" in the 2008 documentation I wrote above so where do you have the information from that there exists such versions?
Maybe I'm completely wrong, anything is possible, but I never read about that. SSRS is part of any SQL Server edition including the Express version (here with additional download).

And, as I said above, the SSRS is independent of a SQL Server installation so reinstalling etc. doesn't affect the SQL Server database part.

Edit: I saw now maybe what you meant: The Sql Server Web Edition. Here is a link which describes what to do to upgrade a Web Edition to a Standard Edition:


As this maybe will also affect the database part of SQL Server during upgrade you will also upgrade SQL Server to the Standard Edition, I don't think it's possible to upgrade only a part of the complete package and leave some other parts in an earlier version. For example, the Express Edition only allows a database size of 4GB and has other limitations and so alle the "add-ons" like SSRS and so on must be adjusted if these limitations doesn't exist anymore.
Normally the installer is intelligent enough to only upgrade the binaries and registry settings but if I were you I would simply install another SQL Server Web Edition machine beside your normal one in the same environment, copy all settings and maybe a database of the old one to this test machine and simply try the upgrade with the installation media like described in the link. Then you can simply test if that works in your environment without any problems and if there are problems you can see them and see what you need to get it run in your environment. After anything works you can then do it with the production machine.



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"):

(where you can amongst others see a "file only installation").

and this one ("Planning and Architecture (Reporting Services)"):

Your very best friend will be this tool after installation ("Reporting Services Configuration Tool"):


leop1212Author Commented:
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
David ToddSenior DBACommented:

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.

leop1212Author Commented:
that did it.
maintenance /version upgrade it just like that!
thank you very much
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.