October 24, 2008 at 6:14 pm
I am new to SQL 2005, and trying to get my head around the SQL Security model. So, at the Server level you add a new login let's call it "test1" using Windows Auth mode. Does this just allow "test1" to connect to the Server and DB?
And then do you need to add a user called "test1" in the Database, users folder, and map the login to the user to give the login access to securables (objects)? Does the user mapping assign the ability to connect to different databases to different users?
Any information on the thinking behind logins, users, user mappings, server roles vs. database roles would be much appreciated.
October 24, 2008 at 10:04 pm
Books On-Line (BOL) is the best place for you to start reading. As you read through the various parts regarding security and still have questions, don't hesitate to jump back here and ask more specific questions.
😎
October 26, 2008 at 9:01 am
fivetenmm (10/24/2008)
So, at the Server level you add a new login let's call it "test1" using Windows Auth mode. Does this just allow "test1" to connect to the Server and DB?And then do you need to add a user called "test1" in the Database, users folder, and map the login to the user to give the login access to securables (objects)? Does the user mapping assign the ability to connect to different databases to different users?
that is exactly how it works. Security logins are created at server level and this enables a user login rights to the server. Users must then be mapped to databases\roles to gain access to data
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply