[dba-SQLServer]Qualifying Object Names

VB, ASP, ASPX, JSP work just fine the way I described.  I guess Jet Engine is not there yet, huh?! :)

Robert Djabarov
Senior SQL Server DBA
USAA IT/DBMS
? (210) 913-3148 - phone
? (210) 753-3148 - pager


 -----Original Message-----
From: 	Arthur Fuller [mailto:artful at rogers.com] 
Sent:	Monday, May 12, 2003 10:59 AM
To:	dba-sqlserver at databaseadvisors.com
Subject:	RE: [dba-SQLServer]Qualifying Object Names

Thanks for the clarification. From the pov of Access, though, I'm not 100%
sure you are correct. I have had forms break because of unqualified record
sources. As soon as I added the prefix "dbo.", said broken forms suddenly
began working as expected. So what you say may apply to the back end, but
I'm not entirely sure it applies to the Access ADP file (and perhaps other
front ends).

Arthur

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Djabarov,
Robert
Sent: May 12, 2003 11:20 AM
To: dba-sqlserver at databaseadvisors.com
Subject: RE: [dba-SQLServer]Qualifying Object Names


Actually, the main reason behind qualifying object names with schema owner
is to eliminate the need for the optimizer to look for the same object under
the schema name of the logged on user.  Following MS best practices, all
objects need to be created by SA.  If that's the case, - the fact that
others are going to use the objects does not require full schema
qualification because after looking for the object of the schema owner of
the logged on user the optimizer will look for the object created by the
database owner.  However, it is a good practice to always fully qualify
object names with schema owner.


_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com