[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 827
  • Last Modified:

PS invoke-sql error catching

I'm using invoke-SQL and it is not catching this error and the program cycles through the all of the tables in the database without telling me there was an issue:
"The statement terminated. The maximum recursion 100 has been exhausted before statement completion."

Is there something wrong with this code? I just need the program to stop and tell me if there's an issue.
Code:
[System.GC]::Collect()
$ErrorActionPreference = "Stop"

PROGRAM CODE HERE

try
{
$CSV = Invoke-Sqlcmd -Query $Query -ErrorAction Stop
}
catch{ [System.Exception]
    $errorout += "major error, query failed problem"
    $errorout += $error[0]
}

MAIN PROGRAM LOOP STARTS HERE
0
johnj_01201
Asked:
johnj_01201
  • 4
1 Solution
 
QlemoDeveloperCommented:
Can you be more specific about "this error"? Is the main loop executed (and Invoke-SQL not part of it)?
0
 
johnj_01201Author Commented:
The program continued to run as normal, showing no results for most of the tables the recursion error was taking place with. I set the recursion level to 32767 in the SQL query to get rid of the  recursion error, but I thought the try\catch code wrapped around the invoke-sql statement would have caught the error and stopped the program to tell me?
0
 
QlemoDeveloperCommented:
So your query is producing recursion (a CTE?), and issues with that are not reflected as exception/error? That might be an issue with Invoke-Sql. I'll try to debug that. It might be necessary you show us the (simplified) query you run.
0
 
QlemoDeveloperCommented:
BTW, the catch doesn't make much sense. [System.Exception] is wrong here: You are adding a string and an ErrorRecord to $errorout.

After catching the error, you continue with the script part "MAIN PROGRAM LOOP STARTS HERE". Is that what you want to do? Providing some more context might be necessary for us to understand.

It would also be interesting to see how the error message should be constructed and displayed (if so).
0
 
QlemoDeveloperCommented:
Tests run successful. If I get recursion error in Invoke-Sql, the exception handler is triggered. This is my test case:
$ErrorActionPreference = "Stop"
remove-variable errorout
$error.Clear()

$Query = @"
with cte as 
( select 1 as no
  union all
  select * from cte
)
select * from cte
"@

try
{
$CSV = Invoke-Sqlcmd -Query $Query -ErrorAction Stop -ServerInstance mssqlserver -Database MyDB -Username Me -Password Secret
}
catch{ 
    $errorout += $error[0]
    Write-Error "major error, query failed problem"
}

Write-Host "... and the story continues ..."

Open in new window

It halts, because of Write-Error, creating another error entry with the custom message.
0

Featured Post

[Webinar] Improve your customer journey

A positive customer journey is important in attracting and retaining business. To improve this experience, you can use Google Maps APIs to increase checkout conversions, boost user engagement, and optimize order fulfillment. Learn how in this webinar presented by Dito.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now