Нет обложки

It is a big heavy book with lots of screen shots and descriptions of each screen shot with some process description. The CD that comes with it is good to search for topics using key words.

Chapter 31 is good - it explains what each of the management views provide.



However, it does not explain how to accomplish something or what the best practice is.

For Example: How do I set up a user login to have read only access to a specific schema? What do I create first a login, schema, or a role? All the security screens seem to have overlapping inputs. I set up a login user. I setup roles. I setup schemas. I create a View but I still only find the dbo schema? What about the other 2 schemas I created? How do I know the security I am setting up will not lock me out of the database next time I login? What is the highest level adimin security I should set and must have - the "super level" that I should not change so I have access and no one else does. Is it possible to check the wrong thing and lock everyone out of the database?

The book tells me what is in each screen and the things I can check off....

The SQL Server 2005 Pocket Consultant explains more on some of these subjects....