Re: Feasibillity of Database Design and Risk Factors Associated

Neither makes sense. One is just half the work of the other and neither will really benefit your Intranet. And if you do go through with it, you better be sure you have bulletproof security. I would advise against it as it doesn't seem like you will get much benefit from recreating the SQL administrator in your site (so tell him that neither requirement makes sense as they both seek to re-invent the wheel on database administration and will require extreme security measures to keep intruders from having a field day with your data.)

"Web Programmer" <jai-hanumanji_at_usa.net> wrote in message news:50227a10.0208162348.3b6ad960_at_posting.google.com...
| Hi,
| Our Client has a Business requirement of creating a web front Database
| design tool on the intranet in asp( ver 3.0 IIS 5.0 ,Sql Server
| 7.0).His requirements are either of one or two :
| Requirement 1 :-
| --------------
| 1.Create all the Database entities on the fly through the web front
| end at the Sql Server back end.The user will input entity attribute
| values in the web front end .asp page (i.e length of the
| column,datatype of the columns, primary keys,foreign key associated
| with the column of other entities created through the same web front
| end).
| On Submit of the page,the table will be created at the backend
| 2.We can also edit the Database tables schema- (length
| variation,datatype change,addition of column,removal of column,rename
| of column)so created from the web front end, provided the columns of a
| table "not" involved in any foreign key relationship with other
| tables can be editable.
| OR
| Requirement 2 :-
| ------------
| Here the entities having parent relationship with child entities will
| be created at the backend only by a Database Administrator and not
| through web front end.
|
| 1.Create Entities( includes : child entities or entities with no
| relation)They on the fly through the front end at the Sql Server
| back end.The user will input schema details at the front end(i.e
| length of the column,datatype of the columns, primary keys,foreign
| keys (with other parent tables only created at the backend) ,default
| value) etc.on Submit of the page,the table will be created at the
| backend
| 2.We can also edit the Database Entities schema created at runtime-
| (length variation,datatype change,addition of column,removal of
| column,rename of column) provided the attributes of an Entity are
| "not" involved in any foreign key relationship with other attributes
| of other Entities.
|
| Right now,We have not made a DDL of the Client's requirement and are
| more concerned about his requirement.
|
| My question :
| Can some Database expert advise me :
|
| 1.Whether Such a design is advisable( Requirements 1 and Requirement
| 2)?
| 2.What will be the risk factors associated with each of the designs(
| Requirement 1 and Requirement 2)?
|
| Kindly help...please...
Received on Sat Aug 17 2002 - 16:30:10 CEST