Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Architecture for "Changing application"

Author  Topic 

tomercagan
Starting Member

1 Post

Posted - 2006-05-21 : 02:19:55
I am developing an application for the Cellular market. The nature of the market means constant changes to the network and those to the solution I am to develop. The changs are usually addition and removel of attributes but sometimes also addition of classes of object. The changes occur every 3-6 months and of course the solution need to be up-to-date... Using a traditional data model (where each class of object has a table with a colunmn for each attribute) may result in constant schema changes. On the other hand a model like the EAV/CR (Entity Attribute Value), which is flexible, raises performance and integrity issues...

Any suggestions? Data to look for?

blindman
Master Smack Fu Yak Hacker

2365 Posts

Posted - 2006-05-22 : 00:31:21
Check into using XML datatypes on SQL Server 2005 instead of EAV schemas.
Go to Top of Page
   

- Advertisement -