Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Public only role slows down

Author  Topic 

bjornh
Yak Posting Veteran

87 Posts

Posted - 2004-01-10 : 05:27:22
Hi,

Here's my problem:
I am using an Access project to control the administration tables. There are only 2 tables that are usefull for administration, so i created an user with only the public Role, and gave the user on the 2 tables the premissions to select, update and delete. But when i open a table, (only 65 rows), the waiting time is allmost 2 times as long compared to when i give the same user db_owner privileges.

How is this possible? And does somebody has solution for it?

Thanks.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-01-12 : 12:29:13
When you say open a table, do you mean with Enterprise Manager?

With db_owner role, it doesn't have to check if you have permissions on the table.

Recommendation, don't use EM to view data. 2nd recommendation is to not grant select, update, insert or delete on tables. Permissions should be granted at the stored procedure level.

Tara
Go to Top of Page

bjornh
Yak Posting Veteran

87 Posts

Posted - 2004-01-12 : 16:53:56
No, Not EM, but Access. I want to Use access for some quick and simple administration. But if i get this correctly, I should only use SP to from my access project?
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-01-12 : 16:59:55
So you are viewing stuff in Access for SQL Server?

And yes, stored procedures are the way to go.

Tara
Go to Top of Page

bjornh
Yak Posting Veteran

87 Posts

Posted - 2004-01-12 : 17:32:22
Jup, access offers a easy way to print reports, etc. And the data still comes from SQL server.. So, i didn't wanted to create an entire application for it..
Go to Top of Page

bjornh
Yak Posting Veteran

87 Posts

Posted - 2004-01-12 : 17:57:09
Mmmmmm

I created a stored procedure (owner ADministration user), but it still takes too much time... isn't there a work around that check?
Go to Top of Page
   

- Advertisement -