Re: SQL Database design question

From: William Cleveland <WCleveland_at_Ameritech.Net>
Date: Mon, 07 Feb 2005 04:23:34 GMT
Message-ID: <a3CNd.1986$ng6.448@newssvr17.news.prodigy.com>

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 Sun Feb 06 2005 - 22:23:34 CST