Another cool thing about extended properties is that, when you add them (for example) to a table or to a column, when you use SSMS to script that table's creation, the script includes adding the current extended properties. So they are easily transferred between databases.
Does anyone besides me find it irritating that you have to know whether a property exists or not and then either add it or insert it? You'd think the system maintenance SPs could be made smart enough to handle this case.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St