Welcome to Dream.In.Code
Getting Help is Easy!

Join 117,163 Programmers for FREE! Ask your question and get quick answers from experts. There are 2,465 online right now! We've got more than 500 tutorials and 2,000 snippets. Join and find out why Dream.In.Code is the #1 programming help community on the internet! Registration is fast and FREE... Join Now!



MSSQL 2000 Permissions

 
Reply to this topicStart new topic

> MSSQL 2000 Permissions, What are:

Mikhail
Group Icon



post 21 Apr, 2008 - 07:21 PM
Post #1


Hello, in this tutorial I am going to explain what permissions are in Microsoft SQL Server 2000.
  • SQL Server 2000
  • Some SQL Experience

So what are permissions?
Permissions are used to determine actions that user(s) can perform on SQL Server or in database. Permissions are usually granted according to group membership(s) and role membership(s), in some cases they are also granted according to login ID, also users must have appropriate permissions before they can do anything that changes database or even accesses data. There are three types of permissions that are used in SQL Server.

Three types of Permissions:
  • Object permissions
    Object permissions control access to the tables,views,columns, and stored procedures. You as a SQL Administrator can control these types of permissions by doing any of the following: Granting, Denying or even Revoking ability to restrict use of any particular statement or stored procedures, you can take this for example: You can grant user the right to SELECT and UPDATE Information, but deny the right to INSERT and DELETE information.
  • Statement permissions
    Statement permissions control administrative actions, such as creating or adding objects to a database. By default members of System Administrators role and Database owners, are allowed such actions, however if there is a normal user, which needs to do something specific to a database such as CREATE RULE or CREATE TABLE, System Administrator and or Database Owner, can grant this type of permission as well revoke it.
  • Implicit permissions
    Implied Permissions, are permissions that come already predefined on System Administrator and Database account(s). Such permissions for a role cannot be changed or applied to other accounts unless these account are made members of a particular role. For example System Administrators can perform any action they want, such as extend database and even kill processes, You can't revoke or assign these right to other account individually they have to be members of a group.

  • Also Database Owners with Implied Permissions can perform any task they want on their database, such as: Delete, add, and change data, That user can also change table's definition and control the table(s) permissions.




This is for anyone who wants to know what permissions in SQL server are for and how they are used, how they may grant them this also explains how the permissions are used, also a notice for anyone who is reading this, when assigning permissions, be careful on what you're assigning, you wouldn't want to give someone untrustworthy permissions that could damage the system.

By: Mikhail of </D.I.C>

Go to the top of the page
+Quote Post


Register to Make This Ad Go Away!


Fast ReplyReply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Lo-Fi Version Time is now: 10/6/08 11:11AM

Live Help!

Tutorials

Programming

Web Development

Reference Sheets

Code Snippets

Bye Bye Ads

Free DIC T-Shirt

T-Shirt Example

Related Sites

Monthly Drawing

Thumb Drive

Partners

Top Contributors

Top 10 Kudos This Month