Comments on: Using aliases in multi-table queries http://www.brentozar.com/archive/2009/04/using-aliases-in-multi-table-queries/ Your technology pain-relief experts. Wed, 08 Feb 2012 16:37:59 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: CrankyRat http://www.brentozar.com/archive/2009/04/using-aliases-in-multi-table-queries/comment-page-1/#comment-8746 CrankyRat Thu, 07 May 2009 00:26:01 +0000 http://www.brentozar.com/?p=3144#comment-8746 Funny, I hate multiple letter alias or full table name alias. That is painful for me. Keeping it to a single letter is my preference. The important thing is to use an alias; the rest is personal preference. The 'dbo' prefix may be recommended but is pretty stupid on the face of it, bloats code and obscures meaning. Having an Oracle background I can't bring myself to use it in this shop. Funny, I hate multiple letter alias or full table name alias. That is painful for me. Keeping it to a single letter is my preference. The important thing is to use an alias; the rest is personal preference. The ‘dbo’ prefix may be recommended but is pretty stupid on the face of it, bloats code and obscures meaning. Having an Oracle background I can’t bring myself to use it in this shop.

]]> By: Brent Ozar http://www.brentozar.com/archive/2009/04/using-aliases-in-multi-table-queries/comment-page-1/#comment-8336 Brent Ozar Mon, 13 Apr 2009 19:25:51 +0000 http://www.brentozar.com/?p=3144#comment-8336 Absolutely, great question. Every table in the database NOW is dbo, but that's not necessarily true for the future. I've seen a lot of projects where a new round of developers or a new project will need to add an additional schema for security needs, and then it's an absolute mess to go back and fix the code everywhere. Absolutely, great question. Every table in the database NOW is dbo, but that’s not necessarily true for the future. I’ve seen a lot of projects where a new round of developers or a new project will need to add an additional schema for security needs, and then it’s an absolute mess to go back and fix the code everywhere.

]]> By: David L. Penton http://www.brentozar.com/archive/2009/04/using-aliases-in-multi-table-queries/comment-page-1/#comment-8335 David L. Penton Mon, 13 Apr 2009 19:25:38 +0000 http://www.brentozar.com/?p=3144#comment-8335 David, See: http://msdn.microsoft.com/en-us/library/ms189915.aspx Microsoft recommends you at least owner-qualifying your object names. Executing User-defined Stored Procedures When executing a user-defined stored procedure (either in a batch or inside a module such as a user-defined stored procedure or function), we strongly recommend qualifying the stored procedure name with at least the schema name. The following example demonstrates the recommended method for executing a user-defined stored procedure. USE AdventureWorks; GO EXEC dbo.uspGetEmployeeManagers 50; -Or- EXEC AdventureWorks.dbo.uspGetEmployeeManagers 50; GO If a nonqualified user-defined stored procedure is specified, the Database Engine searches for the procedure in the following order: * The sys schema of the current database. * The caller's default schema if executed in a batch or in dynamic SQL. Or, if the nonqualified procedure name appears inside the body of another procedure definition, the schema containing this other procedure is searched next. For more information about default schemas, see User-Schema Separation. * The dbo schema in the current database. Important: If any user-created stored procedure has the same name as a system stored procedure, the user-created stored procedure will never be executed if you use a nonschema-qualified name reference. For more information, see Creating Stored Procedures (Database Engine). David,

See: http://msdn.microsoft.com/en-us/library/ms189915.aspx

Microsoft recommends you at least owner-qualifying your object names.

Executing User-defined Stored Procedures

When executing a user-defined stored procedure (either in a batch or inside a module such as a user-defined stored procedure or function), we strongly recommend qualifying the stored procedure name with at least the schema name.

The following example demonstrates the recommended method for executing a user-defined stored procedure.

USE AdventureWorks;
GO
EXEC dbo.uspGetEmployeeManagers 50;

-Or-

EXEC AdventureWorks.dbo.uspGetEmployeeManagers 50;
GO

If a nonqualified user-defined stored procedure is specified, the Database Engine searches for the procedure in the following order:

* The sys schema of the current database.
* The caller’s default schema if executed in a batch or in dynamic SQL. Or, if the nonqualified procedure name appears inside the body of another procedure definition, the schema containing this other procedure is searched next. For more information about default schemas, see User-Schema Separation.
* The dbo schema in the current database.

Important:
If any user-created stored procedure has the same name as a system stored procedure, the user-created stored procedure will never be executed if you use a nonschema-qualified name reference. For more information, see Creating Stored Procedures (Database Engine).

]]> By: David Stein http://www.brentozar.com/archive/2009/04/using-aliases-in-multi-table-queries/comment-page-1/#comment-8334 David Stein Mon, 13 Apr 2009 19:21:27 +0000 http://www.brentozar.com/?p=3144#comment-8334 Brent, is the dbo. really necessary? Is there some reason why that should be included if every table in the database is dbo? Brent, is the dbo. really necessary? Is there some reason why that should be included if every table in the database is dbo?

]]>