Foreign Key/Primary Key GRRR!

Question

Foreign Key/Primary Key GRRR!

Viewing 5 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic. Login to reply

schleep SSChampion Points: 12585 More actions · Answer 1

You didn't say it was a reporting db -- which might have led to the question, Is it necessary to maintain the production relationships in the first place?

Johan Bijnens SSC Guru Points: 135369 More actions · Answer 2

... Is it necessary to maintain the production relationships in the first place ...

- maybe not the actual FK's , but certainly keep the FK-indexes because They will speed up queries !

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

Sorin Petcu Hall of Fame Points: 3195 More actions · Answer 3

So you will come to my solution !

In Theory, theory and practice are the same...In practice, they are not.

schleep SSChampion Points: 12585 More actions · Answer 4

ALZDBA,

What I meant with keeping prod relationships was, for reporting purposes, it's not always the best/fastest way to get at the data. We pre-aggregate some data on the way to the reporting server.

Johan Bijnens SSC Guru Points: 135369 More actions · Answer 5

That's a big 10-4

During pre-aggregate phase, the fk-indexes will speed up the queries wherever possible. The relationships themselves indeed can be dropped.

Keep in mind, that declaring a foreign key doesn't create an index to support the foreign key !

If they are needed/wanted at "reporting" mode that's up to you.