Re: Insert Stored Procedure where the table is provided as input argument
From: Joe Celko (jcelko212_at_earthlink.net)
Date: 11/22/04
- Next message: Joe Celko: "Re: JOIN on multiple conditions"
- Previous message: Steve Kass: "Re: Change returned data in a view based on security role?"
- In reply to: Sarutobi Sama: "Re: Insert Stored Procedure where the table is provided as input argument"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 21 Nov 2004 17:17:47 -0800
>> A little correction is that the crud will be done by users through a
web app so the utility will be just dealing with tables management. <<
Then they are not users; they are DB Administrators with the power to
change the schema. SQL Server comes with tools for that already, so
this utitlity is a bit redundant.
Surely you would NEVER allow end-users to change the schema. That would
mean you have absolutely no data model whatsoever, no data integrity,
etc. These systems fall apart quickly; I estimate about one year after
actual deployment. The reason for the yearly failure is that people
have to do annual reports and that is when the entire scream kludge is
exposed for the disaster it has become.
I consulted for a two companies that have allowed users into the schema.
One gave all programmers full DBA rights in INFORMIX. The tables kept
changing making reporting impossible and they quickly appointed a single
DBA and a Data Manager, then locked the programmers out of the schema.
The other company is now 1/5 the size it was two years ago, heavily
outsourced and most of its former customers have stated in a survey they
will never do business with them again. That is among the customers
that are still in business themselves. Their strategy was to keep
getting new customers to keep revenue ahead of failures. It worked for
107 customers and almost two years :)
--CELKO--
Please post DDL, so that people do not have to guess what the keys,
constraints, Declarative Referential Integrity, datatypes, etc. in your
schema are. Sample data is also a good idea, along with clear
specifications.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
- Next message: Joe Celko: "Re: JOIN on multiple conditions"
- Previous message: Steve Kass: "Re: Change returned data in a view based on security role?"
- In reply to: Sarutobi Sama: "Re: Insert Stored Procedure where the table is provided as input argument"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
