RE: Setting up basic access permissions for simple SQL 2005 db
- From: Hate_orphaned_users <Hateorphanedusers@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 27 Dec 2006 14:52:01 -0800
Remeber if you use a web interface(IIS) to connect to SQL server.
You must setup a connection string in the webpage(asp) if you use SQL user
accounts to connect to sql server and set specific permissions.
If you wan't to connect to SQ server with windows authentication , you must
set IIS to impersonate a windows account you chose and give this account
acces to the database. Also you can set permissions on the folders and
webpages they may open.
There is alot of stuff about this , just google.
I asumed you are using a IIs webserver but the idea is still the same.
You must use windows or SQL account authentication on the webserver.
Good luck!
"sketchy" wrote:
Hello SQL experts,.
Well, after reading, and experimenting with permissions in SQL, I think I've
hit the stage of total confusion when it comes to securing a db for internal
use. Let me describe my desired results.
We have a simple db that has a table that will store our kb information for
our technical support team. This kb info is all stored in one table, yet.
There are other tables in that db, but they are not related to this kb data.
Data will be added/edited via some simple web pages on our intranet.
DomainUser1, DomainUser2, and DomainUser3 all need the ability to read and
write (add records, update info) to the table. All other domain users should
only have read access to this information. I want permissions granted to the
users based simply on their domain accounts.
My problem is that I seem to be reading conflicting information on users and
logins in SQL server, roles, and how to apply this to my situation. Whether
or not I need to create a login for each user, and/or how to apply the
correct permissions for those users to the desired table/view. I'm also
unsure if I should create a view to that table so that it offers me better
control of security. I thought I'd test out my experiments by using simple
UPDATE and CREATE sql statements, but really can't even get that far yet
because of being unsure on how it's best to set up these users.
My questions aren't an excuse for not doing research on my own. Believe me,
I've gone around in circles on this. It's just that after 10 years of doing
general IT administration, being unvoluntarily thrusted into the world of SQL
has left me stumpted.
Any assistance would be REALLY appreciated.
--
Sketchy
- Follow-Ups:
- Prev by Date: Re: Restoring Databases with Encrypted Data to Another Server
- Next by Date: Re: Job owned by a non-sysadmin fails to run
- Previous by thread: Locked out of server?
- Next by thread: RE: Setting up basic access permissions for simple SQL 2005 db
- Index(es):
Relevant Pages
|
|
