Catching an uncaptured error in SQL

SQL Server Ask the Experts
2585 pts.
Tags:
CSV
SQL
SQL Server errors
This is a batch of SQL code I’ve been using: 
BEGIN TRY
begin
BULK INSERT DBXMRPAS2.dbo.[STG_drive] FROM 'Wdmyitpxmdev1xmmsbcpcsvfile20080715drive.200807151100.extracting'
WITH
( MAXERRORS =1000,
FIELDTERMINATOR = '^',
ROWTERMINATOR = '|n'
)
end
END TRY
BEGIN CATCH
SELECT 'Error Caught'
SELECT
ERROR_MESSAGE(),
ERROR_NUMBER()

END CATCH
Why would an error from this statement not be captured by the catch if the .CSV file is missing for the given directory?
Asked: Last updated:
Related Questions

Answer Wiki

Thanks. We'll let you know when a new response is added.

I’m not sure why it isn’t catching the error. I would assume because BULK INSERT is throwing an OS error not a SQL error.

I would recommend checking to see if the file exists prior to attempting the BULK INSERT command. You can do this via the xp_fileexist. You can see an example of use here.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: