Re: question about trusted connections

From: Jining Han <jining.han_at_gmail.com>
Date: 24 Jan 2005 20:38:36 -0800
Message-ID: <1106627916.019257.293890@f14g2000cwb.googlegroups.com>

Each Oracle database server is a database, unless SQLSrv where one instance contains multiple databases.

This being said, it then makes sense that DBO is not applicable inside an Oracle server whereas in SQLSrv, with each server containing multiple databases, all objects are owned by DBO unless created by a user who is not the db owner or who doesn't have SA_ROLE.

Now in each database (Oracle or SQLSrv alike), a user can have its own objects, and they are referenced by user.objects. It just happens that in the majority of SQLSrv applications, objects are owned by DBO, therefore one usually doesn't have to explicity prefix the object with DBO. Oracle gets around this problem via the user of SYNONYMS.

The above is very different from trusted connection. Trusted connections in SQLSrv really means NT-authenticated login. This gets us into IDENTITY management issue, and Oracle and SQLSrv have their own different solutions.

Jining Han Received on Mon Jan 24 2005 - 22:38:36 CST