Re: public role question
- From: "Kalen Delaney" <replies@xxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 24 Apr 2006 10:53:18 -0700
Hi Dan
The user dbo is a privileged user and can create tables and procs, execute
procs, and access data in all the tables. You should try to revoke
permissions from the user dbo.
You have said you created a new user. How are you trying to connect as that
new user?
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Dan D." <DanD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FB897411-12FA-47C0-BDD8-5855475E1A2C@xxxxxxxxxxxxxxxx
It returns 'dbo'.
--
Dan D.
"Dan Guzman" wrote:
What does the query 'SELECT USER' return?
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Dan D." <DanD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2E69E961-1C77-4B9D-9962-F4C11B7017EB@xxxxxxxxxxxxxxxx
In the new database that I created, I was able to create a stored
procedure.
I ran EXEC sp_helprotect NULL, 'public' but I don't see the "create
procedure" permisson listed under the action column. How am I able to
create
a stored procedure with a user that is only a member of public and has
no
other permissions?
--
Dan D.
"Dan D." wrote:
Using SS2000 SP4. I'm trying to lock down the database as much as
possible. I
created a new sql server login and gave the user no permissions other
than
public role.
Why am I able to create a stored procedure with the new user. I
thought
Public had select, insert, update, delete permissions. Does that allow
a
user
to create a stored procedure?
Thanks,
--
Dan D.
.
- Follow-Ups:
- Re: public role question
- From: Dan D.
- Re: public role question
- References:
- Re: public role question
- From: Dan Guzman
- Re: public role question
- Prev by Date: Speed of SQL Authenication vs. Trusted Connection
- Next by Date: Re: public role question
- Previous by thread: Re: public role question
- Next by thread: Re: public role question
- Index(es):
Relevant Pages
|