Anam Verma (9/7/2010)
In the part1, you have mentioned about SELonJN operation, how it can be enabled?
It will be really handly if you'll also post the changes you made to the indexes or query to achieve the better performing execution plans.
I had the same problem when I first read Paul's series. The point to understand here is that Paul is not actually modifying the query in this first part... instead, he's actually enabling and disabling rules in SQL Server and running the same query. I'm thick... it took until part 4 for me to figure that out. ;-)
As he said, he'll get to how to do that later. I recommend that if you ever do that, you do it only on a test server. :-)
I also recommend keeping track of the parts of the series... when you read part 4, you'll be itching to start from the beginning again.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs