How can SQL code behave differently in or outside procedure and about poor error handling

During refactoring of very old code, I found a ancient/ugly and in the end even totally wrong error handling script. Interesting is that the developer probably tested it outside of procedure and it did "kind a work" for him, ... :)

I'll add details later (or much later).

How can I query remote Microsoft SQL Server using integrated security

How can I query remote Microsoft SQL Server without setting up linked server and not using hardcoded username and password of course! :)

tSQLt FakeTable fails with error "cannot be renamed because the object participates in enforced dependencies"

Table is probably included as part of some "schema binded" view. Use attached script to temporary remove schema binding.

Error:
"[Test] failed: (Error) A .NET Framework error occurred during execution of user-defined routine or aggregate "SuppressOutput":
System.Data.SqlClient.SqlException: Object '[dbo].[SomeTable]' cannot be renamed because the object participates in enforced dependencies."


Source on GIT