locked
Keep SSMS on WSUS server?? RRS feed

  • Question

  • I'm creating a new Windows Server 2019 WSUS server.

    SQL Server Management Studio 17.9.1 is being installed so the WID database and log files can be moved to another volume.

    Is there any reason for me to keep SSMS installed after this is done??

    I don't worry too much about database backups since the server is backed up every night.

    I can't think of any other reasons to keep SSMS around...

    Thank you, Tom

    Thursday, February 28, 2019 7:34 PM

All replies

  • Hello Tom,

    If you're not going to maintain the WSUS database, then I don't see a "must" to have the SQL Server Management Studio (SSMS) installed, you can also use the sqlcmd.exe but the SSMS gives the GUI which many might find easier to use.

    The SSMS can be handy for some maintenance tasks, but you can manage without, so in the end the choice is up to you, it's easy to install if you would need it at some point.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, February 28, 2019 8:53 PM
  • Hello, that's what I thought.

    This is SSMS 17.x, which seems pretty hard to remove.

    Have you (or anyone reading this thread) seen any good explanations of how to remove it??
    I know that re-running the same setup program will after awhile show a 'Remove' button but it also leaves a lot of stuff which one might not want to keep...

    Thank you, Tom

    Thursday, February 28, 2019 9:01 PM
  • Yeah it does leave a lot behind, I'm not aware of any tool or method other than manually.

    Below you will find a list of ALL the components that gets installed when you install SQL Server Management Studio 17.9.1

    Name Publisher Version
    Microsoft .NET Framework 4.5 Multi-Targeting Pack Microsoft Corporation 4.5.50710
    Microsoft .NET Framework 4.5.1 Multi-Targeting Pack Microsoft Corporation 4.5.50932
    Microsoft .NET Framework 4.5.1 Multi-Targeting Pack (ENU) Microsoft Corporation 4.5.50932
    Microsoft .NET Framework 4.5.1 SDK Microsoft Corporation 4.5.51641
    Microsoft .NET Framework 4.5.1 Multi-Targeting Pack Microsoft Corporation 4.5.51209
    Microsoft .NET Framework 4.5.1 Multi-Targeting Pack (ENU) Microsoft Corporation 4.5.51209
    Microsoft Help Viewer 2.2 Microsoft Corporation 2.2.23107
    Microsoft ODBC Driver 13 for SQL Server Microsoft Corporation 14.0.1000.169
    Microsoft SQL Server 2012 Native Client Microsoft Corporation 11.3.6540.0
    Microsoft SQL Server 2014 Management Objects Microsoft Corporation 12.0.2000.8
    Microsoft SQL Server 2017 Microsoft Corporation  
    Microsoft SQL Server 2017 Policies Microsoft Corporation 14.1000.169
    Microsoft SQL Server 2017 T-SQL Language Service Microsoft Corporation 14.0.17289.0
    Microsoft SQL Server Data-Tier Application Framework (x86) Microsoft Corporation 14.0.4127.1
    Microsoft SQL Server Management Studio - 17.9.1 Microsoft Corporation 14.0.17289.0
    Microsoft System CLR Types for SQL Server 2014 Microsoft Corporation 12.2402.11
    Microsoft System CLR Types for SQL Server 2017 Microsoft Corporation 14.0.1000.169
    Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.21005 Microsoft Corporation 12.0.21005.1
    Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.21005 Microsoft Corporation 12.0.21005.1
    Microsoft Visual C++ 2013 Redistributable (x64) - 14.0.23026 Microsoft Corporation 14.0.23026.0
    Microsoft Visual C++ 2013 Redistributable (x86) - 14.0.23026 Microsoft Corporation 14.0.23026.0
    Microsoft Visual Studio 2015 Shell (Isolated) Microsoft Corporation 14.0.23107.10
    Microsoft Visual Studio Tools for Applications 2015 Microsoft Corporation 14.0.23829
    Microsoft Visual Studio Tools for Applications 2015 Language Support Microsoft Corporation 14.0.23107.20

    You might want to open a new thread in the SQL Server forums and ask the experts there if they know a good method: SQL Server  >  SQL Server Tools


    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Thursday, February 28, 2019 9:32 PM
    Thursday, February 28, 2019 9:32 PM
  • Uninstalling only the the SQL Server Management Studio will also remove the following components:

    • Microsoft System CLR Types for SQL Server 2017
    • Microsoft SQL Server 2017 Policies
    • Microsoft SQL Server 2017
    • Microsoft SQL Server 2012 Native Client


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, February 28, 2019 9:52 PM
  • I asked as you suggested, who knows what will happen?? :)
    Thursday, February 28, 2019 10:04 PM
  • Hi Tom,
      

    It is a pleasure to answer your question.
      

    As an integrated environment, SSMS provides tools for configuring, monitoring, and managing SQL instances. For the working mechanism of WSUS, the installation of SSMS is not necessary. However, from the perspective of future maintenance, SSMS can provide some maintenance tasks in a relatively straightforward manner. 
      

    As Leon explains, it's very handy to perform tasks and easy to install, so uninstalling or not depends on your habits.
      

    The most common method is to uninstall via Control Panel's Add/Remove Programs. 
    If SQL Server Management Studio does not appear in Add/Remove Programs, execute the SQL Server Management Studio installer again to uninstall or repair it.
      

    Hope the above can help you.
      

    Regards,
    Yic Lv

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, March 1, 2019 6:16 AM