Answer Posted / gaurav

Yes. This situation occurs in one-to-one relationships.

For example:

create table Table1
( T1_Id integer not null primary key
, T1_Data varchar(9) not null
)
create table Table2
( T2_Id integer not null primary key
, T2_Data varchar(37) not null
, foreign key (T2_Id) references Table1 (T1_Id)
)

Why would someone design two tables like this? If it's a
one-to-one relationship, couldn't you just include T2_Data
in Table1? Yes, you could, although then you would also need
to allow T2_Data to be NULL, if not every T1_Id has a
matching T2_Id—in this case it's actually a
one-to-zero-or-one relationship.

If it's a true one-to-one relationship, where every T1_Id
has a matching T2_Id, then you could combine them without
NULLs. Then the only reason why you might want separate
tables would be if T2_Data were (a) infrequently queried,
and (b) so large that it would result in many fewer physical
rows on a physical database page, which would imply poorer
performance for queries that used only T1_Data.

What are the fixed server level roles? : sql server security

1130

---

What is the contrast amongst drop and truncate?

1034

---

What are the different types of sql server replication? : sql server replication

1273

---

What do you mean by collation recursive stored procedure?

1056

---

How to replace given values with null using nullif()?

991

---

How do you manipulate data?

910

---

Explain external key management in sql server 2008

889

---

What does normalization do to data?

1073

---

Is it true, that there is no difference between a rule and a check constraint?

1058

---

Suppose you want to implement the many-to-many relationships while designing tables. How would you do it?

1006

---

Explain the truncate command?

986

---

How to trouble shoot if unable to connect SQL Server

1992

---

Explain the categories of stored procedure?

937

---

What is SQL Azure Data sync?

121

---

explain different types of cursors? : Sql server database administration

1090

---