Skip to main content

Finding Foreign Key In SQL Server

Here I Will explain how many ways, we can find a foreign key in SQL Server.

 Using this query, we can find all the foreign keys in the current database.
select * from sysobjects where type='f'
Using this query, we can find all the foreign keys in a selected table.
EXEC sp_fkeys 'Catalog'
Using this query, we can find all the foreign keys in a current database with more information.
SELECT RC.CONSTRAINT_NAME FK_Name  
, KF.TABLE_SCHEMA FK_Schema  
, KF.TABLE_NAME FK_Table  
, KF.COLUMN_NAME FK_Column  
, RC.UNIQUE_CONSTRAINT_NAME PK_Name  
, KP.TABLE_SCHEMA PK_Schema  
, KP.TABLE_NAME PK_Table  
, KP.COLUMN_NAME PK_Column  
, RC.MATCH_OPTION MatchOption  
, RC.UPDATE_RULE UpdateRule  
, RC.DELETE_RULE DeleteRule  
FROM INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS RC  
JOIN INFORMATION_SCHEMA.KEY_COLUMN_USAGE KF ON RC.CONSTRAINT_NAME = KF.CONSTRAINT_NAME  
JOIN INFORMATION_SCHEMA.KEY_COLUMN_USAGE KP ON RC.UNIQUE_CONSTRAINT_NAME = KP.CONSTRAINT_NAME
Labels:
Location: Pune, Maharashtra, India

Comments

Post a Comment

Popular posts from this blog

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

What to choose between .NET Core and .NET?

 .NET Framework is a better choice if you: you don't have enough time time to learn new technology. Need a stable environment to work in. Have nearer release schedules. you are already working on an existing app and extending its functionality. If already have an existing team with .NET expertise and building production-ready software. Do not want to deal with continuous upgrades and changes. Building Windows client applications using Windows Forms or WPF .NET Core is a better choice if you: IF you wanted to deploy your app on Windows, Linux, and Mac operating systems. Are not afraid of learning new things. Are not afraid of breaking and fixing things since .NET Core is not fully matured yet. When you are learning .NET. work on open source.
Post a Comment
Read more