• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 9. SQL Server Security > Security Introduced

Security Introduced

Access security is very limited and does not provide you with a lot of protection. This is because you must grant read, write, and delete permissions to the users of an Access database for the network share on which the database resides. This makes the database vulnerable to hackers as well as the inadvertent actions of users (for example, accidentally moving or deleting a file). Furthermore, you cannot integrate Access security with the operating system. This means that users must log on to both the operating system and Microsoft Access. Furthermore, operating system features such as password aging, the logging of user activity, and the logging of invalid login attempts are all unavailable with Microsoft Access.

As mentioned in the chapter introduction, SQL Server offers a very robust and flexible security model. SQL Server 2000 security is tightly integrated with Windows NT 4 and Windows 2000 security. This means that SQL Server can utilize the users and roles that you set up at the operating system level. Within SQL Server, you determine the rights that the users and roles have for the various SQL Server objects. Not only are Windows users and roles available, but you can also take advantage of operating system features such as password expiration and the logging of login attempts and database activities.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint