Powershell Sql query Timing out

Code below work fine. But there arew times it falls into issues. The issues is with the timeout value. Is there a way have it not time out. There are times the query can take 2 or 3 minutes and theirs no issue.Sometimes query can take 3 to 6 hours and it works its just that theres a lot of records to process in SQL Studio the query works fine no timeout. When it starts to take that long when executed from Powershell it timesout.

My question is how to I code this so it does not time out. I put in a parameter but it a time value for time out can I have it where it wont time out and let the query run its course.


add-pssnapin sqlserverprovidersnapin100 -ErrorAction SilentlyContinue
add-pssnapin sqlservercmdletsnapin100 -ErrorAction SilentlyContinue


$Servers = Get-Content "C:\NOCScripts\SQL\AuditPending\AuditPendingLog.txt"

Foreach($server in $Servers){

invoke-sqlcmd -inputfile "C:\NOCScripts\SQL\AuditPending\AuditRecords.sql" -serverinstance $server -database "master" -QueryTimeout 20000 

}

Open in new window

LVL 8
Leo TorresSQL DeveloperAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Bob LearnedCommented:
What version of SQL Server are you using?

According to this Connect article, you should be able to use query timeout of 0 in SQL Server 2012 and higher.

invoke-sqlcmd -querytimeout 0 still times out
https://connect.microsoft.com/SQLServer/feedback/details/551799/invoke-sqlcmd-querytimeout-0-still-times-out
0
Leo TorresSQL DeveloperAuthor Commented:
using 2008 mostly few 2005.
Have not tried -querytimeout 0 option will to that today. and keep you posted.

thanks
0
Bob LearnedCommented:
I believe that before SQL Server 2012, the minimum timeout value was 0, so you would have to set the timeout very high.  The max value appears to be 65534.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Leo TorresSQL DeveloperAuthor Commented:
OK great I will go with that for now. I Have not been able to test.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Powershell

From novice to tech pro — start learning today.