×

Loading...
Ad by
  • 最优利率和cashback可以申请特批,好信用好收入offer更好。请点链接扫码加微信咨询,Scotiabank -- Nick Zhang 6478812600。
Ad by
  • 最优利率和cashback可以申请特批,好信用好收入offer更好。请点链接扫码加微信咨询,Scotiabank -- Nick Zhang 6478812600。

Help! Newbie question regarding SQL server 2005

Hi, all:

I want to complete the following tasks in SQL server 2005:

1. Create a database named 'A' (I know how to do this)
2. Determine a user account to use to access A
3. Grant create and drop tables privilege for A to this user account
and ensure the user account is a member of db_ddladmin role.
4. Need to know the userID and password for this user account.

What confuses me is that the server has a 'security' folder which includes logins and server roles;
then each database has a 'security' folder which includes users and roles.
Can someone clarify the above concepts?

Can someone provide step-by-step instructions as to how to complete the above 2, 3 and 4 step?
Thank you so much.
Report

Replies, comments and Discussions:

  • 工作学习 / 专业技术讨论 / Help! Newbie question regarding SQL server 2005
    Hi, all:

    I want to complete the following tasks in SQL server 2005:

    1. Create a database named 'A' (I know how to do this)
    2. Determine a user account to use to access A
    3. Grant create and drop tables privilege for A to this user account
    and ensure the user account is a member of db_ddladmin role.
    4. Need to know the userID and password for this user account.

    What confuses me is that the server has a 'security' folder which includes logins and server roles;
    then each database has a 'security' folder which includes users and roles.
    Can someone clarify the above concepts?

    Can someone provide step-by-step instructions as to how to complete the above 2, 3 and 4 step?
    Thank you so much.
    • Let me try to answer your questions
      Each server/instance can have more than one database. The common security folder has all user logins. With each login, you can assign its permission to each database. Role is the same but better for management. Common sense is, you assign permission to role, then, join login to role which make the login has same permission as role. For example, if a role has tons of logins, and one day you want to change a permission, you don't need to change each login. One touch on role can solve the problem.

      On each database, you can see the assigned logins/roles. So, it is a two way process. Either way will work.

      Right-click on login, select properties, you can assign which database this user login can access and its permission.

      My two cents.