Issue with Powershell 7.2 SqlServer module

Shwetha J 10

I've installed the SqlServer module into Azure runbooks for powershell 7.2 but when I go to use it I get... "Invoke-Sqlcmd' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again." Runs on powershell 5.1 no problem

3 answers

Ryan Hill 28,106 Reputation points Microsoft Employee

2024-02-23T01:26:45.9533333+00:00
Hi @Shwetha J
I was not able to get this to work and the SqlServer module running on Automation Account PowerShell 7.2 is a known issue. Attempting to install the module resulted in

Error: Install-Module: Line | 2 | Install-Module SqlServer -AllowClobber -SkipPublisherCheck -Force -Sc … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | NuGet provider is required to interact with NuGet-based repositories. Please ensure that '2.8.5.201' or newer version of NuGet provider is installed.

Installing the Nuget-based provider via Install-PackageProvider -Name NuGet -Force didn't resolve the issue either. Checking PowerShell Gallery | SqlServer.psm1 22.2.0 shows that 22.2.0 requires PowerShell 7.2.1 or higher. Even though I wasn't getting this message and considering that it does work in PowerShell 5.1, I'm inclined to think that currently the SqlServer module is not supported in 7.2 for Automation Account, as others have stated in this open GitHub issue.
Please sign in to rate this answer.

2 people found this answer helpful.
Somesh Bhalerao 5 Reputation points

2024-04-05T14:41:07.8266667+00:00

I want to communicate with SharePoint Online using PnP power-shell, which force me to use Framework 7.2 and in same code I want to execute SQL command on Azure SQL instance. Which framework should I go for.

Somesh Bhalerao 5 Reputation points

2024-04-06T05:39:33.0833333+00:00

User Framework 7.2 and instead of SqlServer module use Invoke-SqlCmd2

It solves my issue, as I do not need to use framework 5.1, by using framework 7.2 I can use PnP Sharepoint Online commands as well.

I hope SqlServer module will be more mature in coming days.

$databaseUser = "SQLUserName" $databasePwd = "SQLUserPassword" $SQL="select * from TempTable" [SecureString]$SecurePass = ConvertTo-SecureString $databasePwd -AsPlainText -Force [System.Management.Automation.PSCredential]$Cred = New-Object System.Management.Automation.PSCredential($databaseUser, $SecurePass) $ReSQL=Invoke-SqlCmd2 -Query $SQL -ServerInstance $databaseServer -Database $databaseName -Credential $Cred $ReSQL.Count
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Vahid Ghafarpour 21,240 Reputation points

2024-02-22T05:10:29.5133333+00:00

Thanks for posting your question in the Microsoft Q&A forum.

Ensure that the SqlServer module is installed in your Azure environment

Install-Module SqlServer

** Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful **
Please sign in to rate this answer.

1 person found this answer helpful.
Shwetha J 10 Reputation points

2024-02-22T05:19:06.83+00:00

SqlServer module is successfully Installed

Shwetha J 10 Reputation points

2024-02-22T06:33:56.1166667+00:00

SqlServer module is successfully Installed but still we see the same error

Francisco Lozada 0 Reputation points

2024-03-18T20:14:23.3066667+00:00

After endless try-error attempts, what worked for me was to set the powershell runtime environment to 5.1, and import the sqlserver version 21.0.17199. Other than that, I kept obtaining the error: Invoke-Sqlcmd: The term 'Invoke-Sqlcmd' is not recognized as a name of a cmd.......

Somesh Bhalerao 5 Reputation points

2024-04-06T05:39:02.46+00:00

User Framework 7.2 and instead of SqlServer module use Invoke-SqlCmd2

It solves my issue, as I do not need to use framework 5.1, by using framework 7.2 I can use PnP Sharepoint Online commands as well.

I hope SqlServer module will be more mature in coming days.

$databaseUser = "SQLUserName" $databasePwd = "SQLUserPassword" $SQL="select * from TempTable" [SecureString]$SecurePass = ConvertTo-SecureString $databasePwd -AsPlainText -Force [System.Management.Automation.PSCredential]$Cred = New-Object System.Management.Automation.PSCredential($databaseUser, $SecurePass) $ReSQL=Invoke-SqlCmd2 -Query $SQL -ServerInstance $databaseServer -Database $databaseName -Credential $Cred $ReSQL.Count

Francisco Lozada 0 Reputation points

2024-04-06T13:21:25.69+00:00

Thank you, super helpful update.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Rich Matheisen 46,711 Reputation points

2024-03-18T22:49:06.3566667+00:00

Rather than running version 5.1, try adding the -UseWindowsPowerShell switch to the Import-Module cmdlet.

PowerShell 7 uses only CORE elements .Net and many modules require more extensive coverage.

Note that PowerShell versions before version 6 are Windows version of PowerShell, Version 6 and 7 are cross-platform versions with no dependencies on Windows.
Please sign in to rate this answer.

1 person found this answer helpful.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Issue with Powershell 7.2 SqlServer module

3 answers

Your answer