Re: SQL Database design question

Erland Sommarskog wrote:

> The more normal way to do this in SQL Server is to expose procedures
> that performs the tasks and necessary integrity checking. Then you
> disallow direct access to the table, and hope that people who have admin
> access from Query Analyzer know what they are doing.
>

I've gone that route, and it should work. The problem is when you're not the DBA, and a later developer slips something past the DBA that doesn't follow your rules.

I'm afraid I don't have a good solution, except for the suggestion I've made at work that both the DBA *and* the original database designer sign off on changes in a database. So far, no luck.

Bill Received on Mon Feb 07 2005 - 05:23:34 CET