Post reply

Uninstall SSRS If you are not using it

  • May 26, 2008 at 10:29 pm

    #380676

    Comments posted to this topic are about the item Uninstall SSRS If you are not using it

    [font="Verdana"]--www.sqlvillage.com[/size][/font]

  • May 26, 2008 at 10:34 pm

    #820331

    There is a good reason for this error, here:

    Reporting Services is not an unplanned installation.

  • May 27, 2008 at 1:01 am

    #820375

    Nice article but if you googled first you could hit the reporting service first. Generally when I get a new error I google it.........:)

  • May 27, 2008 at 2:16 am

    #820404

    Saying that you will Google the error is all very well but don't forget that someone has to highlight and document these "features" in the first place. Well done for writing the article.

  • May 27, 2008 at 5:24 am

    #820459

    Thanks for the article - it is to the point and focused.

    It made me think of the components of SQL that I have installed and know that I do not use them and should get around to removing them - but never have. (on my laptop - not on production servers)

    Thanks

    Kevin

  • May 27, 2008 at 6:03 am

    #820484

    At first glance, I tend to disagree. I don't always know which features will be used in the long-term on a new SQL Server. So I install AS,IS and RS. Then I install the latest Service Pack. (If I install RS later, I will have to reapply the Service Pack to fully patch that new module)

    And by having it already installed, it is ready to use if/when we decide to use that feature.

    Of course I agree with stopping the services related to an unused product.

    This is just my practice.

  • May 27, 2008 at 6:47 am

    #820521

    In general, it's a good idea to reduce the surface area of a server by disabling unused services. This includes Reporting Services, integration services, IIS, etc....

  • May 27, 2008 at 7:34 am

    #820554

    this error came after a year from date of installation. when service was already disabled.

    [font="Verdana"]--www.sqlvillage.com[/size][/font]

  • May 27, 2008 at 8:11 am

    #820573

    John Bates (5/27/2008)

    At first glance, I tend to disagree. I don't always know which features will be used in the long-term on a new SQL Server. So I install AS,IS and RS. Then I install the latest Service Pack. (If I install RS later, I will have to reapply the Service Pack to fully patch that new module)

    And by having it already installed, it is ready to use if/when we decide to use that feature.

    Of course I agree with stopping the services related to an unused product.

    This is just my practice.

    This practice is flawed. Best Practice dictates that you should install only what you need. If you aren't sure, then someone who is should be performing the installation.

    As for the guy saying "If you had googled first" I would submit that little relevant information would be returned. This is a case of an experienced DBA using his knowledge along with a little bit of testing to resolve an error that is generally not documented.

    Well done. Nice article. And now a google search WILL return relevant information for DBAs who run into the same issue.

  • May 27, 2008 at 8:54 am

    #820591

    Tend to agree with you above. Don't install something you don't need.

  • May 27, 2008 at 9:51 am

    #820643

    good information, thank you Mohan!

  • May 28, 2008 at 2:16 pm

    #821461

    The following one liner will uninstall SSRS silently - replace [font="Courier New"]/qn[/font] with [font="Courier New"]/qb[/font] if you want to see the progress of the uninstall:

    [font="Courier New"]setup.exe /qn REMOVE=RS_Server,RS_Web_Interface,RS_tools INSTANCENAME=myinstance[/font]

    The default instance name is MSSQLSERVER

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply