SA0253 : The current database is hardcoded in object reference

Directly referencing the current database within your SELECT, UPDATE, DELETE, INSERT, MERGE, and EXECUTE statements by using fully qualified names can lead to future complications. This arises when such hardcoded references make your SQL scripts less flexible and harder to maintain.

For example:

1-- Example of problematic query with hardcoded database reference
2SELECT * FROM CurrentDBName.SchemaName.TableName;

Using the database name directly in queries can be problematic if you move the code to another database or change the database name. This practice hinders the portability of your code across different environments and complicates updates.

• Reduces script portability when deploying code across multiple databases.

• Increases difficulty in maintaining codebase, especially during database migrations or name changes.

Avoid using hardcoded database identifiers in SQL statements to improve script portability and maintainability.

Follow these steps to address the issue:

1. Identify any SQL statements that include hardcoded database names within the object identifiers, such as “CurrentDBName.SchemaName.TableName”.

2. Remove the database name part from the identifiers to allow SQL Server to automatically resolve to the current database at runtime. This will replace “CurrentDBName.SchemaName.TableName” with “SchemaName.TableName”.

3. Review the remaining schema names to ensure they are necessary or appropriately scoped for your queries.

4. Test the modified queries to ensure they function as expected without the hardcoded database context.

For example:

1-- Example of corrected query without the database reference
2SELECT * FROM SchemaName.TableName;

The rule has a Batch scope and is applied only on the SQL script.

Rule has no parameters.

The rule requires Analysis Context. If context is missing, the rule will be skipped during analysis.

Design Rules, Bugs

There is no additional info for this rule.

Other Resources