This document introduces SQL Server administrators and developers to the new security features of SQL Server 2000. In addition to outlining the new features, there is a detailed discussion about how to best implement security in a Microsoft Windows® 2000 domain environment as well as source code examples.
Designing your application so that Stored Procedures are the only database objects that are accessed is generally the best practice. Agree? Disagree? Read this article by guest columnist Mindy Curnutt to see what she thinks!
The following stored procedure will demonstrate the use of cursor metadata. Using cursor metadata we can get information about an SQL statement and use that information to dynamically generate other code such as HTML or other stored procedures.
In this month's article I will cover an aspect of SQL Server that always generates a great deal of, well, shall we say "discussion"—triggers. Love them or hate them, SQL Server 2000 will change they way you think about triggers and will probably alter the way you design your applications. Specifically, this month I will dive into cascading referential integrity (RI) and the new INSTEAD OF and AFTER trigger concepts in SQL Server 2000.