SCENARIO
Entering your office room, you find a note from your boss concerning confidential and private information given out to users accessing the newly set up table Employees , and he states that he urgently needs you to find a solution. With the number of users accessing your database, it is likely that many will pry into the leaked information, so you must finish this task at the earliest possible time. Your boss states that he may receive objections from employees about disclosed personal information, such as salary, from the newly created Employees table. You know your boss is waiting for an answer so you quickly look for a solution. ANALYSISYou quickly investigate the SQL Server Books Online and seem to find a solution. You are astonished to find such a simple solution that can be applied in less than five minutes. The solution is the view. Because you have a stronger background in the administration of SQL Server, you may have not known how to implement a view, which is often considered to be a design topic. Then you scroll down to the bottom of the article and find that a view may also be implemented with the easy-to-use interface of the SQL Server Enterprise Manager. Relieved, you read on to learn how to actually limit the rows and columns using the apparent power of the view. You come across a term called "filtering" and learn that it means selecting or deselecting columns (vertical) or rows (horizontal). You implement a filtering view strategy, so that users see only what they need to see, and decide to learn more about the development side of SQL Server 2000. |