How to know sql server database foreignkey & primary key list

Question

0.00/5 (No votes)

See more:

Hi ,
As i need to know the database Foreign keys & Primary keys list due to i need to insert from database1 to database2 at that time i need to drop the Foreign keys, Primary keys off the database2 so that i can insert the Data's of database1 after that i need to recreate the keys

Note : i got the query for foreign keys list but when i try to drop Foreign keys at that time i getting primary key reference error

thanking you for your help soon!!

Posted 23-Apr-12 19:15pm

AZAD88

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sandeep Mewara · Answer 1 · 2012-04-23T19:34:00

Who suggested/asked you to do the migration this way? Do you have any idea on how much data issues can be introduced this way? There was/is a reason why Primary key & Foreign keys are defined. I would not suggest you to do this way at all.

Instead try:
1. Have a look at the database design properly. make a list of tables in a sequence where the lowest tables having maximum dependencies and top once being kind of master table with only primary keys.
2. Populate/Migrate the table from top to bottom order - First the master tables and then the dependent tables.

This way you wont need to drop any key and the data would have least chance of getting corrupt.

I would suggest you to talk to your senior and get more guidance in case you need more help on the same.

Mehdi Gholam · Answer 2 · 2012-04-23T20:28:00

Solution 2

It is generally a bad idea to do this, but sometimes you need to do it for bulk inserts.

You can disable constraint checking, see here :
http://weblogs.sqlteam.com/joew/archive/2008/10/01/60719.aspx[^]

Posted 23-Apr-12 20:28pm

Mehdi Gholam

Comments

AZAD88 24-Apr-12 4:21am

Thanks for u r comments i have already analysis issues & i have explained too but no use here i am in freak situation that y i posted with a hope !!