Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

problem with users tables, views, and SPs having (dbo) at the end

Status
Not open for further replies.

drctx

IS-IT--Management
May 20, 2003
226
US
i have an adp that i finally got working right, but domain admins are the only ones that can run the adp and not have all the tables and queries have (dbo) at the end, regular domain users get tables and queries that look like this:
tablename (dbo)
viewname (dbo)
storedprocedurename (dbo)

i've tried renaming them and it doesn't help.

any suggestion on removing the (dbo) other than making everyone an admin?
 
It must be related to permissions. Explain your setup.

1. Who is the database owner i.e. dbo?
2. How are the permissions set for the objects (tables, views, sp's). by role? individual user? NT domain?
3. Do you use NT Authentication or do the users login into SQL Server?
 
1. the database owner is dbo.
2. NT domain
3. NT Authentication

i'm using access 2002 with ms sql server 7 running on win2k.
win i login in as testuser with domain user rights is when i get the (dbo) added to object names. if i go to user manager and add doman admin to testuser, then login the (dbo) is gone and the database works correctly. i've tried adding owner and admin to testuser in enterprise manager's users but it didn't work.
 
It sounds like you are using NT domain as the user in the database. This is a good way to go for administration. What you did is what was necessary by adding testuser to NT domain. Is that not okay?
 
i figured out what the problem was. the reports couldn't find any queries becuase of the (dbo) at the end. i found that in the report properties/data record source qualifier if i put in dbo, everything works properly now.

thanks for the help.
 
That doesn't really solve the problem.
The others that use it that don't have (dbo) will not be able to connect.
 
It seems like you would need to add the user to AD power user or local power user, or something along those lines. Does anyone out there know? I only have one user that this is happening to, and all users have the same permissions on the SQL box. I even log into her machine and have no problems.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top