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 different types of lock modes in sql server 2000?

995

---

what are statistics, under what circumstances they go out of date, how do you update them? : Sql server database administration

999

---

What is an index. What are the types?

1162

---

Explain about extended stored procedure?

993

---

What is dirty page?

1035

---

SQL Server Architecture ?

2522

---

Explain the characteristics of a transaction server for example atomicity, consistency, isolation, durability?

1181

---

What is difference between foreign key and unique key?

1048

---

What is difference between index and primary key?

1138

---

Difference between drill down and drill through report.

1003

---

What is normalization? Explain different forms of normalization?

1229

---

Explain boyce and codd normal form(bcnf)?

1015

---

Can we install sql server 2016 on windows 7?

1199

---

Can we join two tables without primary key?

1095

---

What is ddl and dml commands?

959

---