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.
| Author |
Topic |
|
slyth
Starting Member
1 Post |
 Posted - 2012-11-24 : 10:37:08
|
| A vendor of ours has structured the data so that all data entities are grouped within a single entity for all relations, stating that this may provide performance benefits when using SQL Server. I have never seen such a weird way of going about normalization of data, however I might not be experienced in "avante-garde" designs. For example,PersonDBID PersonID PersonName PersonAddress ClientDBID ClientID ClientName ClientAddress ClientTelephoneDBID represents a company database. So logically each DBID refers to a separate database, whilst physically each entity would have its own DBID so that the SQL developer would be able to query each database separately. This might create some duplication of data since the DBID has to be stored as a field in each row of data.I am not a certified SQL Server administrator, however, from a conceptual point of view I saw the design as logic which does not make any sense to me, however, I would like your opinion about it.Jon |
|
|
namman
Constraint Violating Yak Guru
285 Posts |
Posted - 2012-11-25 : 23:47:52
|
| Could you provide example in more detail (with data and sample queries)? |
 |
|
|
Bustaz Kool
Master Smack Fu Yak Hacker
1834 Posts |
Posted - 2012-11-26 : 14:27:49
|
| How many actual databases are there? From your description, it sounds like there is a common database that is used to point to a company specific database. Is this true?=================================================We are far more concerned about the desecration of the flag than we are about the desecration of our land. -Wendell Berry |
|
|
|
|
|
|
Database structure enigma