|
|
There is no such thing as too much security. The days of valuing ease of use over security are past. Code samples in computer articles and books from an earlier time often described how to log into SQL Server with the sa login and no password. Nowadays, database developers and DBAs acknowledge that such practices jeopardize the safety of corporate networks.
Building secure solutions is similar to any other computer topic. You have to learn the concepts, discover how to implement those concepts, and then refine your security designs, just as you do the layout and behavior of your databases and forms. Furthermore, practice makes perfect. No database application should be put on a network without being secure. Therefore, you will have many opportunities to enhance your understanding of and ability to implement secure database solutions.
This chapter offers four sections to help you along your way to building secure solutions. The chapter commences with an overview of SQL Server security concepts. This first section aims to introduce you to core security notions and show how they interact with Access projects. Next, the chapter presents an introduction to SQL-DMO (SQL Distributed Management Objects). This is a hierarchical object model in the style of many Office object models that you can use to administer SQL Server instances. The SQL-DMO review illustrates database security and other uses for the object model, such as exploring database objects as well as attaching and detaching database files. The last two sections deal with logins, users, roles, and permissions. These concepts interact to determine who can do what on a SQL Server instance and its databases.
|
|