Re: Sql permissions headache
- From: "Mike C#" <xyz@xxxxxxx>
- Date: Tue, 22 Aug 2006 15:22:37 -0400
Are you using Integrated security or SQL Authentication?
"bill" <bill@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:482EB4F8-7055-405A-AD5F-F2B3A6D68AE1@xxxxxxxxxxxxxxxx
In many of our older sql databases I find that the users were all made
"dbo".
I was told this is because no one really knew the minimum permissions
needed
by the apps that accessed the database. (I'm afraid that this practice
may
creep into production databses.)
Read and write permissons are easy to address but stored procs are harder.
We are always adding new ones to a DB and, if we don't make all users dbo,
we
need to explicitly add permissions to each stored proc. At least that's
what
I think we need to do.
Can you suggest a better approach to determine the minimum permissions
needed to access a database?
Bill
.
- Prev by Date: Re: Anyone from MS?
- Next by Date: Re: OSQL Batch File Problem
- Previous by thread: secure query results
- Next by thread: Re: Sql permissions headache
- Index(es):