Viewing 15 posts - 5,011 through 5,025 (of 5,678 total)
SSIS can't handle this to my knowledge.
What you're going to look to do is build a generic table with a VARCHAR(MAX) field in it, and use that as your original...
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 10, 2010 at 12:18 pm
This should help:
CREATE NONCLUSTERED INDEX idx_temp_forGuidCounts ON TEMP ( GUID, Results)
This should let your count statements avoid a scan on the clustered and go directly for a seek on the...
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 10, 2010 at 12:01 pm
Alright,
For starters, these are estimated plans. Everything here is a guess by the optimizer. By preference, you always want to work with actuals.
That said.
The original plan is doing...
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 10, 2010 at 11:59 am
I'd take a multi-step approach to this.
First, I'd break down the XML into a series of sub tables for filtering. Basically a series of #tmps or @tmps.
Next, I'd use...
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 10, 2010 at 11:47 am
We'd need to know the DDL and index builds on TEMP to be able to help further.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 10, 2010 at 11:44 am
jfong-786685 (11/9/2010)
I have attached the sqlplans on the first post.
Attached plans are 0 bytes each. No data in them, just the file names. Please double check?
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 10, 2010 at 11:16 am
sejal p gudhka (10/8/2010)
My questions is why do you require select into another table in same database ?
I've done it on rare occassions to produce flattened results during overnight rebuilds...
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 10, 2010 at 11:12 am
Jeff Moden (11/10/2010)
Craig Farrell (11/9/2010)
And back on topic for the thread:http://www.sqlservercentral.com/Forums/Topic1018016-338-1.aspx
*wallbanger*
I'll be "blah blah"ing over in the corner now.
As I said on that post... now I know what a feeding...
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 10, 2010 at 10:49 am
eric larocca (11/9/2010)
It should process the order by after it gathers the records
whats inside...
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 10, 2010 at 10:14 am
Use a temp table and store your variables in rows and join against it instead of trying to use the IN statement that way.
IE:
DECLARE @filter TABLE (FilterVal VARCHAR(100))
INSERT INTO @filter...
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 9, 2010 at 7:53 pm
snoop123 (11/9/2010)
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 9, 2010 at 7:51 pm
The higher selectivity probably lets it seek instead of scan an index. Would have to see the DDL and the comparable sqlplans to tell for sure.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 9, 2010 at 7:45 pm
It's either late, or I'm blind. Where's the tweak?
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 9, 2010 at 6:39 pm
Alright, this is a bit chewy. This code works under the following conditions:
- Start or end time falls between Friday 23:00 and Monday 7:00.
- Noone works...
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 9, 2010 at 4:46 pm
The last row found in the reference table is the last value entered/updated into the target table.
An easy test:
CREATE TABLE #tmp (ID1 INT, Val1 VARCHAR(10))
CREATE TABLE #tmp2 (ID2 INT, Val2...
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 9, 2010 at 3:53 pm
Viewing 15 posts - 5,011 through 5,025 (of 5,678 total)