Post reply

How to deal with SqlServer PS module

  • March 27, 2020 at 1:38 pm

    #3738237

    I understand that SqlServer has replaced SQLPS.  I experienced this with SQL 2017.  I'm now putting together a SQL 2019 with server 2019 and I see that SQLPS is still part of an install.

    PS C:\Windows\system32> get-module sqlps -ListAvailable

    Directory: C:\Program Files (x86)\Microsoft SQL Server\150\Tools\PowerShell\Modules

    ModuleType Version Name ExportedCommands

    ---------- ------- ---- ----------------

    Manifest 15.0 SQLPS {Backup-SqlDatabase, Save-SqlMigrationReport, Invoke-Polic...

    Before I do an install of SqlServer module, is it advised to uninstall SQLPS first?  I did try to install SqlServer without trying to remove SQLPS and I'm then presented with all sorts of red text

    PackageManagement\Install-Package : The following commands are already available on this system:'Add-SqlAvailabilityDatabase,Add-SqlAvailabilityGroupListenerStaticIp,Add-SqlFirewallRule,Backup-SqlDatabase,blah blah blah....'. This module 'SqlServer' may override the existing commands. If you still want to install this module 'SqlServer', use -AllowClobber parameter.

    Should one just -AllowClobber?  When I do that, both SQLPS and SqlServer appear to be installed.

    Please advise and thanks!

    • This topic was modified 5 years, 2 months ago by NotBob.
    • This topic was modified 5 years, 2 months ago by NotBob.

  • March 28, 2020 at 2:10 pm

    #3738625

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • March 31, 2020 at 2:35 pm

    #3739300

    Since I'm not getting much for suggestions on this topic, is there another source or forum that might be able to assist?

    Thanks!

  • October 27, 2020 at 4:56 pm

    #3801772

    I'm experiencing exactly the same issue. Cannot use a certain function of invoke-sqlcmd because of the sqlps module installed with 2019 and cannot seem to remove it and replace it with sqlserver.

     

     

Viewing 4 posts - 1 through 4 (of 4 total)

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

Cookies on SQLServerCentral

This website stores cookies on your computer.

These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.

To find out more about the cookies we use, see our Privacy Policy