December 30, 2013 at 9:21 am
GilaMonster (12/30/2013)
Revenant (12/30/2013)
For performance tuning, I would reword it as "Measure often, tune when needed."I was just thinking exactly that.
That's beautiful. It lacks the familiarity of the well-known phrase, but is more accurate for what we really do. I admit the original title had me immediately. I'm not a writer, but is this a case where you draw someone in with the title and then refine it later in the article?
December 30, 2013 at 11:17 am
wolfkillj (12/30/2013)
GilaMonster (12/30/2013)
wolfkillj (12/30/2013)
is there really a performance problem or are you just "tuning" the query as a knee-jerk response to seeing a scan in the execution plan or some similar shibboleth?Exactly.
I'm tired of all the threads 'help me get rid of joins', 'how do I force an index seek', 'which join type performs worst', etc, etc.
Title comes from http://en.wiktionary.org/wiki/measure_twice_and_cut_once
I like the title itself, too. I got the reference immediately - the "measure twice, cut once" maxim has saved me a good bit of aggravation in carpentry and woodworking projects.
Of course, "measure twice, cut once" really only refers to one of two possible error states - measuring too long/large and having to cut again to get the correct length/size. The other error state could probably be covered by the maxim, "measure twice, avoid a second trip to Home Depot."
Pfft. You can't avoid a second trip to Home Depot! That's a myth. All you can do is make it as inexpensive a second trip as possible.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
December 30, 2013 at 11:19 am
Happy Holidays everyone! May the new year bring you interesting learning, growth, and fulfillment.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
December 30, 2013 at 11:27 am
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
GilaMonster (12/30/2013)
wolfkillj (12/30/2013)
is there really a performance problem or are you just "tuning" the query as a knee-jerk response to seeing a scan in the execution plan or some similar shibboleth?Exactly.
I'm tired of all the threads 'help me get rid of joins', 'how do I force an index seek', 'which join type performs worst', etc, etc.
Title comes from http://en.wiktionary.org/wiki/measure_twice_and_cut_once
I like the title itself, too. I got the reference immediately - the "measure twice, cut once" maxim has saved me a good bit of aggravation in carpentry and woodworking projects.
Of course, "measure twice, cut once" really only refers to one of two possible error states - measuring too long/large and having to cut again to get the correct length/size. The other error state could probably be covered by the maxim, "measure twice, avoid a second trip to Home Depot."
Pfft. You can't avoid a second trip to Home Depot! That's a myth. All you can do is make it as inexpensive a second trip as possible.
Not true! I've actually completed a couple projects without second trips to Home Depot in the last few months. Of course, that's because I'm in the habit of buying 150% of the amount of everything I may possibly need for any given project. That way, if I didn't get it in the shopping trip for the current project, odds are that I have it in the surplus materials from previous projects.
Jason Wolfkill
December 30, 2013 at 11:33 am
wolfkillj (12/30/2013)
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
GilaMonster (12/30/2013)
wolfkillj (12/30/2013)
is there really a performance problem or are you just "tuning" the query as a knee-jerk response to seeing a scan in the execution plan or some similar shibboleth?Exactly.
I'm tired of all the threads 'help me get rid of joins', 'how do I force an index seek', 'which join type performs worst', etc, etc.
Title comes from http://en.wiktionary.org/wiki/measure_twice_and_cut_once
I like the title itself, too. I got the reference immediately - the "measure twice, cut once" maxim has saved me a good bit of aggravation in carpentry and woodworking projects.
Of course, "measure twice, cut once" really only refers to one of two possible error states - measuring too long/large and having to cut again to get the correct length/size. The other error state could probably be covered by the maxim, "measure twice, avoid a second trip to Home Depot."
Pfft. You can't avoid a second trip to Home Depot! That's a myth. All you can do is make it as inexpensive a second trip as possible.
Not true! I've actually completed a couple projects without second trips to Home Depot in the last few months. Of course, that's because I'm in the habit of buying 150% of the amount of everything I may possibly need for any given project. That way, if I didn't get it in the shopping trip for the current project, odds are that I have it in the surplus materials from previous projects.
How do you buy 150% of a hammer? 😛
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
December 30, 2013 at 11:37 am
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
GilaMonster (12/30/2013)
wolfkillj (12/30/2013)
is there really a performance problem or are you just "tuning" the query as a knee-jerk response to seeing a scan in the execution plan or some similar shibboleth?Exactly.
I'm tired of all the threads 'help me get rid of joins', 'how do I force an index seek', 'which join type performs worst', etc, etc.
Title comes from http://en.wiktionary.org/wiki/measure_twice_and_cut_once
I like the title itself, too. I got the reference immediately - the "measure twice, cut once" maxim has saved me a good bit of aggravation in carpentry and woodworking projects.
Of course, "measure twice, cut once" really only refers to one of two possible error states - measuring too long/large and having to cut again to get the correct length/size. The other error state could probably be covered by the maxim, "measure twice, avoid a second trip to Home Depot."
Pfft. You can't avoid a second trip to Home Depot! That's a myth. All you can do is make it as inexpensive a second trip as possible.
Not true! I've actually completed a couple projects without second trips to Home Depot in the last few months. Of course, that's because I'm in the habit of buying 150% of the amount of everything I may possibly need for any given project. That way, if I didn't get it in the shopping trip for the current project, odds are that I have it in the surplus materials from previous projects.
How do you buy 150% of a hammer? 😛
You don't. The key is to buy at least one new tool with every project. That way, you already have the specific hammer you'll need for the next project. I can always think of at least one new tool I need. 😀
With supplies for a project, that's where you just buy extra.
December 30, 2013 at 11:49 am
Ed Wagner (12/30/2013)
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
GilaMonster (12/30/2013)
wolfkillj (12/30/2013)
is there really a performance problem or are you just "tuning" the query as a knee-jerk response to seeing a scan in the execution plan or some similar shibboleth?Exactly.
I'm tired of all the threads 'help me get rid of joins', 'how do I force an index seek', 'which join type performs worst', etc, etc.
Title comes from http://en.wiktionary.org/wiki/measure_twice_and_cut_once
I like the title itself, too. I got the reference immediately - the "measure twice, cut once" maxim has saved me a good bit of aggravation in carpentry and woodworking projects.
Of course, "measure twice, cut once" really only refers to one of two possible error states - measuring too long/large and having to cut again to get the correct length/size. The other error state could probably be covered by the maxim, "measure twice, avoid a second trip to Home Depot."
Pfft. You can't avoid a second trip to Home Depot! That's a myth. All you can do is make it as inexpensive a second trip as possible.
Not true! I've actually completed a couple projects without second trips to Home Depot in the last few months. Of course, that's because I'm in the habit of buying 150% of the amount of everything I may possibly need for any given project. That way, if I didn't get it in the shopping trip for the current project, odds are that I have it in the surplus materials from previous projects.
How do you buy 150% of a hammer? 😛
You don't. The key is to buy at least one new tool with every project. That way, you already have the specific hammer you'll need for the next project. I can always think of at least one new tool I need. 😀
With supplies for a project, that's where you just buy extra.
Many of my projects are just excuses to acquire tools. Sometimes, they're even vehicles for obscuring the fact that a tool was even purchased. Recently, for example, after telling my wife that we needed a new shower valve because I couldn't remove a screw with a broken head from the old, leaky one, I took one more stab at it and got the screw out. We no longer needed a new valve, but just coincidentally, a set of shower valve wrenches cost about the same as a new valve. Now, the faucet doesn't leak and I don't have to make awkward use of vise grips and channel locks to remove those valves any more. I call that a win-win.
Jason Wolfkill
December 31, 2013 at 1:53 am
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
GilaMonster (12/30/2013)
wolfkillj (12/30/2013)
is there really a performance problem or are you just "tuning" the query as a knee-jerk response to seeing a scan in the execution plan or some similar shibboleth?Exactly.
I'm tired of all the threads 'help me get rid of joins', 'how do I force an index seek', 'which join type performs worst', etc, etc.
Title comes from http://en.wiktionary.org/wiki/measure_twice_and_cut_once
I like the title itself, too. I got the reference immediately - the "measure twice, cut once" maxim has saved me a good bit of aggravation in carpentry and woodworking projects.
Of course, "measure twice, cut once" really only refers to one of two possible error states - measuring too long/large and having to cut again to get the correct length/size. The other error state could probably be covered by the maxim, "measure twice, avoid a second trip to Home Depot."
Pfft. You can't avoid a second trip to Home Depot! That's a myth. All you can do is make it as inexpensive a second trip as possible.
Not true! I've actually completed a couple projects without second trips to Home Depot in the last few months. Of course, that's because I'm in the habit of buying 150% of the amount of everything I may possibly need for any given project. That way, if I didn't get it in the shopping trip for the current project, odds are that I have it in the surplus materials from previous projects.
How do you buy 150% of a hammer? 😛
Buy a bigger hammer than you need. A bodge hammer.
If it doesn't fit, hit it with a hammer. If it still doesn't fit, get a bigger hammer 😀
For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden
December 31, 2013 at 4:15 am
ChrisM@Work (12/31/2013)
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
GilaMonster (12/30/2013)
wolfkillj (12/30/2013)
is there really a performance problem or are you just "tuning" the query as a knee-jerk response to seeing a scan in the execution plan or some similar shibboleth?Exactly.
I'm tired of all the threads 'help me get rid of joins', 'how do I force an index seek', 'which join type performs worst', etc, etc.
Title comes from http://en.wiktionary.org/wiki/measure_twice_and_cut_once
I like the title itself, too. I got the reference immediately - the "measure twice, cut once" maxim has saved me a good bit of aggravation in carpentry and woodworking projects.
Of course, "measure twice, cut once" really only refers to one of two possible error states - measuring too long/large and having to cut again to get the correct length/size. The other error state could probably be covered by the maxim, "measure twice, avoid a second trip to Home Depot."
Pfft. You can't avoid a second trip to Home Depot! That's a myth. All you can do is make it as inexpensive a second trip as possible.
Not true! I've actually completed a couple projects without second trips to Home Depot in the last few months. Of course, that's because I'm in the habit of buying 150% of the amount of everything I may possibly need for any given project. That way, if I didn't get it in the shopping trip for the current project, odds are that I have it in the surplus materials from previous projects.
How do you buy 150% of a hammer? 😛
Buy a bigger hammer than you need. A bodge hammer.
If it doesn't fit, hit it with a hammer. If it still doesn't fit, get a bigger hammer 😀
I'm assuming this is the approach you took to getting the hob installed in your new kitchen. How many hammers exactly did you need to buy?
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
December 31, 2013 at 4:39 am
dwain.c (12/31/2013)
ChrisM@Work (12/31/2013)
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
GilaMonster (12/30/2013)
wolfkillj (12/30/2013)
is there really a performance problem or are you just "tuning" the query as a knee-jerk response to seeing a scan in the execution plan or some similar shibboleth?Exactly.
I'm tired of all the threads 'help me get rid of joins', 'how do I force an index seek', 'which join type performs worst', etc, etc.
Title comes from http://en.wiktionary.org/wiki/measure_twice_and_cut_once
I like the title itself, too. I got the reference immediately - the "measure twice, cut once" maxim has saved me a good bit of aggravation in carpentry and woodworking projects.
Of course, "measure twice, cut once" really only refers to one of two possible error states - measuring too long/large and having to cut again to get the correct length/size. The other error state could probably be covered by the maxim, "measure twice, avoid a second trip to Home Depot."
Pfft. You can't avoid a second trip to Home Depot! That's a myth. All you can do is make it as inexpensive a second trip as possible.
Not true! I've actually completed a couple projects without second trips to Home Depot in the last few months. Of course, that's because I'm in the habit of buying 150% of the amount of everything I may possibly need for any given project. That way, if I didn't get it in the shopping trip for the current project, odds are that I have it in the surplus materials from previous projects.
How do you buy 150% of a hammer? 😛
Buy a bigger hammer than you need. A bodge hammer.
If it doesn't fit, hit it with a hammer. If it still doesn't fit, get a bigger hammer 😀
I'm assuming this is the approach you took to getting the hob installed in your new kitchen. How many hammers exactly did you need to buy?
Heh funny you should say that. Whilst GF's dad was building the extension doing the heavy stuff (pretty darned cool for a 67-year old) and I was working on the interior, that was the running joke because all we could hear was banging.
We completed the spare bedroom just in time for visitors at Xmas but I hadn't had time to fit a handle on the door. Two had failed. One of them didn't turn enough to pull the latch all the way, the other has a manufacturing problem. So on Xmas morning, mom removes her bag from the back of the door, tugs on the hole where the handle fits, and nothing happens because the bottom of the door is stuck fast in the new carpet. We're all downstairs swigging on the Cava with carols blaring out of the HiFi and she's stuck in there for 30 minutes, shouting and stamping on the floor!
For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden
December 31, 2013 at 5:33 am
The rest of this week ought to be...
Interesting...
Some fun things, some not-so-fun things...
Tomorrow I'm going to be shivering and cheering at the NHL Winter Classic (Go WINGS!) considering they're predicting a high of 19F (about -7.2C for everyone on a rational temp scale) and it's being held in an outdoor football (US, not soccer) stadium.
Then Saturday, we get to do less fun things...
Take our two cats to the vet for checkups, and help the mom-in-law move...
yay
Thankfully, she's just moving down one floor in her building to a more wheelchair accessible apartment, but annoyingly no one else on the wifes' side of the family is available to help Saturday.
December 31, 2013 at 7:58 am
ChrisM@Work (12/31/2013)
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
GilaMonster (12/30/2013)
wolfkillj (12/30/2013)
is there really a performance problem or are you just "tuning" the query as a knee-jerk response to seeing a scan in the execution plan or some similar shibboleth?Exactly.
I'm tired of all the threads 'help me get rid of joins', 'how do I force an index seek', 'which join type performs worst', etc, etc.
Title comes from http://en.wiktionary.org/wiki/measure_twice_and_cut_once
I like the title itself, too. I got the reference immediately - the "measure twice, cut once" maxim has saved me a good bit of aggravation in carpentry and woodworking projects.
Of course, "measure twice, cut once" really only refers to one of two possible error states - measuring too long/large and having to cut again to get the correct length/size. The other error state could probably be covered by the maxim, "measure twice, avoid a second trip to Home Depot."
Pfft. You can't avoid a second trip to Home Depot! That's a myth. All you can do is make it as inexpensive a second trip as possible.
Not true! I've actually completed a couple projects without second trips to Home Depot in the last few months. Of course, that's because I'm in the habit of buying 150% of the amount of everything I may possibly need for any given project. That way, if I didn't get it in the shopping trip for the current project, odds are that I have it in the surplus materials from previous projects.
How do you buy 150% of a hammer? 😛
Buy a bigger hammer than you need. A bodge hammer.
If it doesn't fit, hit it with a hammer. If it still doesn't fit, get a bigger hammer 😀
In my other life as a stagehand, sometimes getting a dodgy piece of a set to line up correctly requires the application of the microadjustment tool.
Jason Wolfkill
December 31, 2013 at 10:18 am
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
GilaMonster (12/30/2013)
wolfkillj (12/30/2013)
is there really a performance problem or are you just "tuning" the query as a knee-jerk response to seeing a scan in the execution plan or some similar shibboleth?Exactly.
I'm tired of all the threads 'help me get rid of joins', 'how do I force an index seek', 'which join type performs worst', etc, etc.
Title comes from http://en.wiktionary.org/wiki/measure_twice_and_cut_once
I like the title itself, too. I got the reference immediately - the "measure twice, cut once" maxim has saved me a good bit of aggravation in carpentry and woodworking projects.
Of course, "measure twice, cut once" really only refers to one of two possible error states - measuring too long/large and having to cut again to get the correct length/size. The other error state could probably be covered by the maxim, "measure twice, avoid a second trip to Home Depot."
Pfft. You can't avoid a second trip to Home Depot! That's a myth. All you can do is make it as inexpensive a second trip as possible.
+10
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 31, 2013 at 10:22 am
wolfkillj (12/30/2013)
...Many of my projects are just excuses to acquire tools. Sometimes, they're even vehicles for obscuring the fact that a tool was even purchased.
Winner Winner Chicken Dinnner
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 31, 2013 at 10:30 am
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
Stefan Krzywicki (12/30/2013)
wolfkillj (12/30/2013)
GilaMonster (12/30/2013)
wolfkillj (12/30/2013)
is there really a performance problem or are you just "tuning" the query as a knee-jerk response to seeing a scan in the execution plan or some similar shibboleth?Exactly.
I'm tired of all the threads 'help me get rid of joins', 'how do I force an index seek', 'which join type performs worst', etc, etc.
Title comes from http://en.wiktionary.org/wiki/measure_twice_and_cut_once
I like the title itself, too. I got the reference immediately - the "measure twice, cut once" maxim has saved me a good bit of aggravation in carpentry and woodworking projects.
Of course, "measure twice, cut once" really only refers to one of two possible error states - measuring too long/large and having to cut again to get the correct length/size. The other error state could probably be covered by the maxim, "measure twice, avoid a second trip to Home Depot."
Pfft. You can't avoid a second trip to Home Depot! That's a myth. All you can do is make it as inexpensive a second trip as possible.
Not true! I've actually completed a couple projects without second trips to Home Depot in the last few months. Of course, that's because I'm in the habit of buying 150% of the amount of everything I may possibly need for any given project. That way, if I didn't get it in the shopping trip for the current project, odds are that I have it in the surplus materials from previous projects.
How do you buy 150% of a hammer? 😛
Seems easy, mostly. just buy what you need and another either half as big or twice as big. Or buy different sorts: If you know you will need a sledge hammer, you buy two different sizes. If you need a small ball and pane hammer, you get a light tack hammer as well just in case. You buy a pane and claw hammer with your lump hammer. If you want a wedge and pane hammer get a large one and a medium one.
Tom
Viewing 15 posts - 42,496 through 42,510 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply