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 |
|
shapper
Constraint Violating Yak Guru
450 Posts |
 Posted - 2010-07-08 : 19:17:50
|
| Hello,What is the best way to create two tables with a One to One relationship?Thanks,Miguel |
|
|
slimt_slimt
Aged Yak Warrior
746 Posts |
Posted - 2010-07-08 : 23:18:25
|
| if your data model and your data are trully in one-to-one relationship in both tables, i suggest you to use one table only. it will be faster for your application and query results retrieval as well as your database will be normalised. |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-07-09 : 03:29:47
|
| We have some 1:1 tables - particularly where we want AUDIT on some of the columns, and other (non audit) columns are very high turnover. For example, hierarchy tables where we also store tree path and "walking order" sequence.We have identical Primary Key column(s) on both tables (but the secondary table has a prefix to the column names) |
|
|
|
|
|
|
One To One Relationship