 |
Alex, Vindicated
[reply]
|
03/02/06 09:01 AM EST
posted by JER email web |
|
Long ago, Alex made a comment that Foreign Keys are great in development but should not be copied to the production server because they reduce performance. SQL Server Central explores the issue and comes to the same conclusion. Though it seems almost academic on most sites, it could definitely improve performance of your nascarnet.coms...
|
|
|
|
Jer, Woot! Thanks for pointing out this article. Since I now work on another site that gets about 1,000,000-10,000,000 page views a day, depending on the time of year and current events in the DC area, I am glad to hear my inability to accept the fact that somehow my database should make up where my business and data tier come up short, is finally starting to pay off.
Then again, the next thing we hear is that using LEFT JOIN for every join is more efficient than just a plain old INNER JOIN.
Alex |
|
[reply]
|
03/09/06 01:12 PM EST
posted by Doug1 web |
|
Alex, doesn't that site run on Access though? :-o
I've thought in terms of inner joins for a long time when I know the
data should follow those constraints, but after it didn't a couple
times, I started making it a more common practice to use Left Joins
when the desired result is mostly interchangable. Why would this be
more efficient though or are you just being facetious? |
|
|
|
Alex is making fun of Bull, who exclusively uses LEFT JOINs, arguing that he would rather get some data back than no data. That is often true, but there are clearly times when a developer would prefer a null resultset to a resultset with a few unexpectedly null columns.
This whole argument has no bearing on shinydonkey.com, though, as I outsource all SQL scripting to villagers in Lesotho, where they only use RIGHT JOINS. |
|
Note: Only registered ShinyDonkey.com users
can post images. Only administrators can delete images.