-
database design
i have a large database that handles almost 10 lac consumers...the interesting thing is none of the tables in here are related...i.e a relational model is not followed....the database is used just as a repository citing performance gains and maintenance simplicity...the result being too many redundant data.
most of the neccessary relations between the entities are captured in a seperate interface in code.. again for performance.....
is this design better than a relational database model....?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|