Apr 17 2020
I have been using
Invoke-sqlcmd with a Querytimeout 0 to get infinite timeout period on Windows 2008 R2 server using SqlPs module.
Upgraded the server to Windows 2016 server and installed SqlServer powershell module. Now my Invoke-sqlcmd is timing out the queries after 30 seconds for the Querytimeout configuration 0.
I have been looking for a documentation that talks about this behavior change and could not find one. Is there a way to get back the original behavior?
I have some practical issues in specifying a very high timeout value for Invoke-sqlcmd.
Your help is appreciated.