Viewing 15 posts - 751 through 765 (of 7,631 total)
Personally, I am about convinced that this is an Optimizer bug of some kind, and that it is also the direct cause of the bad plan in this case.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 2, 2010 at 10:24 am
Paul White (3/2/2010)
Are you asking about the Row Goal thing I said I'd have a look for? I didn't look yet :blush:
But it really is just a case of...
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 2, 2010 at 10:22 am
And you know, this would all be a lot easier and simpler if you did this in a set-based way, instead of using a CURSOR and WHILE loops.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 2, 2010 at 8:29 am
Adi already answered your question. Did you do what he said?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 2, 2010 at 8:17 am
Paul, did you come with anything on the bad rowcount issue? I'm afraid it's really bugging me... :unsure:
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 2, 2010 at 7:53 am
rbrenan (3/2/2010)
SELECT
column1_output, column2_output
FROM
table1 t
INNER JOIN
containstable(table1, column1_search, '"searchterm"') ct ON ct. = table1.id
I have a nonclustered index on column1_search with...
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 2, 2010 at 7:50 am
whoa! Did you know that this is embedding subordinate elements inside of text content? I'm not even sure if that's valid XML...
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 2, 2010 at 6:31 am
you'll probably get more answers to this question in one of the five different SSRS forums, here: http://www.sqlservercentral.com/Forums/Group416.aspxp
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 1, 2010 at 8:22 pm
RBarryYoung (3/1/2010)
agustingarzon (3/1/2010)
The approach is ok, but it's making a clust-ix-scan that scans through the...
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 1, 2010 at 8:10 pm
grnlt (3/1/2010)
but if you are using SSRS and the report is needing to pull data from up to the minute time, isnt dynamic SQL the only way to go?
Most of...
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 1, 2010 at 8:02 pm
agustingarzon (3/1/2010)
The approach is ok, but it's making a clust-ix-scan that scans through the first...
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 1, 2010 at 12:06 pm
Paul White (3/1/2010)
RBarryYoung (3/1/2010)
Paul White (3/1/2010)
Still a risk of the optimizer choosing a merge join with that one, Barry.
True, but I prefer to try to get the optimizer to "do...
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 1, 2010 at 11:24 am
Paul White (3/1/2010)
...The optimizer is seriously under-estimating the cost of scanning that clustered index.
...
Yes, that's the big question here, why is it doing that? It's RowCount estimate is ...
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 1, 2010 at 11:22 am
Paul White (3/1/2010)
Still a risk of the optimizer choosing a merge join with that one, Barry.
True, but I prefer to try to get the optimizer to "do the right thing"...
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 1, 2010 at 11:17 am
Paul White (3/1/2010)
The text file in the ZIP is empty 🙁The problem in your execution plan was the merge join. A poor choice by the optimizer.
Paul
Hmm, I thought that...
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 1, 2010 at 11:04 am
Viewing 15 posts - 751 through 765 (of 7,631 total)