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.
Steve Jones reviews Robert Viera's Professional SQL Server Programming text.
We've got a new guest columnist! Click here to find out a little bit about Mindy Curnutt, then read her first article for SqlServerCentral.com.
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!
This article presents the technical details of the page layout for data in SQL Server 6.5
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.
The downturn in the economy has left quite a few technical people out of work. This ongoing article describes the experiences over the past two years of Steve Jones. Reader experiences are requested and the article will be updated weekly.
By Steve Jones
vicarous – adj. curious to know what someone else would do if they were...
Say we have a database that we want to migrate a copy of into...
We are trying to get apps and users off of using SQL accounts to...
Hi I have this view to check if a job is running: SELECT...
All, if you are like me and do not care for the built-in color...
Certain internal SQL Server actions cause internal checkpoints. Which of these actions does not cause an internal checkpoint?
See possible answers