Skip to main content

Difference Between Primary key, Unique key And Foreign Key.

The difference between Primary key, Unique key and Foreign Key is the most common interview question for .NET as well as SQL developers.

 The PRIMARY Key and UNIQUE Key constraints, both are similar and enforce uniqueness of the column on which they are defined.


Primary Key

  • A primary key cannot have a NULL value.
  • Each table can have only one primary key.
  • By default, Primary key is clustered index, and the data in the database table is physically organized in the sequence of the clustered index.
  • A primary key can be related to other tables as a Foreign Key.
  • We can generate ID automatically with the help of Auto Increment field. Primary key supports Auto Increment value.
  • We can define a Primary key constraint on temporary table and table variable. 
  • We can't delete a primary key value from the parent table which is used as a foreign key in the child table. To delete we first need to delete that primary key value from the child table.


Unique Key

  • Unique Constraint may have a NULL value.
  • Each table can have more than one Unique Constraint.
  • By default, Unique key is a unique non-clustered index.
  • Unique Constraint cannot be related to another table's as a Foreign Key.


Foreign Key


  • A foreign key is a field in the table that is Primary key in another table.
  • A foreign key can accept multiple null values.
  • A foreign key does not automatically create an index, clustered or non-clustered. You can manually create an index on the foreign key.
  • We can have more than one foreign key in a table.
  • Foreign keys do not automatically create an index, clustered or non-clustered. You must manually create an index on foreign keys.
  • There are actual advantages to having a foreign key be supported with a clustered index, but you get only one per table. What's the advantage? If you are selecting the parent plus all child records, you want the child records next to each other. This is easy to accomplish using a clustered index.
  • Having a null foreign key is usually a bad idea instead of NULL  referred to as "orphan record".
  • We can’t define a foreign key constraint on a temporary table or table variable.
  • We can delete the foreign key value from the child table even though that refers to the primary key of the parent table.

Labels

Labels:
Location: United States

Comments

Post a Comment

Popular posts from this blog

How To See Logs Of Dropped Tables From The Database in MS SQL.

Here, I will explain you how you can see logs of users. Step 1 : First, create a new database with name "test". Step 2 : Create a new table. Step 3 : Now, go and drop the table by running the following command. Step 4 : Now, select your database under Object Explorer and go to Reports >> Standard Reports >> Schema Changes History. Step 5 : You will then see the schema change history. The report will show you who has dropped this table. Finally, you can locate the user activity with the help of log.
Post a Comment
Read more

How To Implement NLog With WebAPI In Asp.Net(C#).

What is NLog? NLog is a flexible and free logging platform for various .NET platforms, including .NET standard. NLog is easy to apply and it includes several targets (database, file, event viewer). Which platform support it? .NET Framework 3.5, 4, 4.5, 4.6 & 4.7 .NET Framework 4 client profile Xamarin Android Xamarin iOS Windows Phone 8 Silver light 4 and 5 Mono 4 ASP.NET 4 (NLog.Web package) ASP.NET Core (NLog.Web.AspNetCore package) .NET Core (NLog.Extensions.Logging package) .NET Standard 1.x - NLog 4.5 .NET Standard 2.x - NLog 4.5 UWP - NLog 4.5 There are several log levels. Fatal : Something terrible occurred; the application is going down  Error : Something fizzled; the application might possibly proceed Warn : Something surprising; the application will proceed  Info : Normal conduct like mail sent, client refreshed profile and so on.  Debug : For troubleshooting; the executed question, the client confirmed, ...
1 comment
Read more

How to write Unit Tests in .net

Unit tests are automated tests that verify the behavior code like methods and functions. Writing unit tests is crucial to clean coding, as they help ensure your code works as intended and catches bugs early in the development process. I can share some tips for writing effective unit tests: Write tests for all public methods Every public method in your code should have a corresponding unit test. This helps ensure that your code behaves correctly and catches any unexpected behavior early. public class Calculator { public int Add(int a, int b) { return a + b; } } [TestClass] public class CalculatorTests { [TestMethod] public void Add_ShouldReturnCorrectSum() { // Arrange Calculator calculator = new Calculator(); int a = 1; int b = 2; // Act int result = calculator.Add(a, b); // Assert Assert.AreEqual(3, result); } } Test boundary conditions  Make sure to test boundary conditions, such a...
Post a Comment
Read more