invoke-sqlcmd does not return T-SQL Errors by cmille19

Hello Kyle,
We have a fix for this issue. Please let us know if you would be willing to help us validate this fix on your test machine



Thanks
Sethu Srinivasan [MSFT]

Any update on where this is fixed? It appears to still be broken. However, If you put a select statement prior to the statement that is in error, it seems the errors are made available.

This returns nothing - regardless of what you put in as OutputSqlErrors or SeverityLevel:
invoke-sqlcmd -ServerInstance ".\SQL2012" -Query 'select 1/0'

This returns an error:
invoke-sqlcmd -ServerInstance ".\SQL2012" -Query 'select 1;select 1/0'

As does this:
invoke-sqlcmd -ServerInstance ".\SQL2012" -Query 'select 1;select 1/0' -OutputSqlErrors $true

This does not (which is expected behavior):
invoke-sqlcmd -ServerInstance ".\SQL2012" -Query 'select 1;select 1/0' -OutputSqlErrors $false

If you use InputFile, the leading select statement must be within the batch (between GO statements) that the error occurs. Running a select at the beginning of the file does not work for errors in a different batch.

Thanks!

This connect was marked as fixed. What version and SP/CU is it fixed in? Can you provide any details?

I am working with Powershell v3 ISE on Windows Server 2008 R2. I cannot figure out how to execute "only" a stored procedure specified in the -Query parameter of Invoke-Sqlcmd and get back any SQL error. This includes any use of -ErrorVariablea-OutputSqlErrors1-Verbose-AbortOnError-ErrorActionStop.

I am testing with divide by zero in a sproc. The error returns as expected in SSMS, SSIS, Sqlcmd from cmd prompt and '& Sqlcmd' in PowerShell. Invoke-Sqlcmd does return errors from a SELECT statement or from a stored procedure like this -Query "SELECT 1;EXEC dbo.usp_WithError".