Hardcoded current database name in procedure call

It is better to avoid using hardcoded references to the current database as this causes problems if you later do the inconceivable by changing the database name or cut-and-pasting a routine. A hardcoded database name has no performance advantage.

Available in

SQL Code Guard

Didn't find what you were looking for?