When using GOTO statement, code that should be reviewed inside the GOTO statement is showing with issues underlined. "The multi-part identifier 'ep_view.MemberNumber' could not be bound".

Would be nice if the code was analyzed as it would be executed so these errors are not present. Takes away from the effectiveness of using SQL Complete.

While I don't use GOTO as a habit, this is a large VIEW that runs faster inside so a GOTO to the code at the end works well. Then a simple command can load it only on the initial run and save time for following TESTING since it is already loaded in the temp file.

IF OBJECTID('tempdb..#tmpExchangePremiumEffDateView') IS NULL
GOTO ExchangePremiumEffDateView