Viewing 15 posts - 19,126 through 19,140 (of 22,226 total)
Is the data loaded through XML being filtered later in the query? If so, use either a permanent table or a temporary table. If not, if the data is doing...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 10, 2008 at 7:46 am
Pull a previous copy out of source control...
If you don't have your code under source control, here's the wake-up call to get it there.
You can't retrieve a previous copy from...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 10, 2008 at 7:42 am
Msg 208, Level 16, State 1, Line 1
Invalid object name 'S_TIMEZONE_TEMP'
Then supply the correct table name. You should get in the habbit of supplying the schema too, so that it...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 10, 2008 at 7:07 am
That's great. Thanks for following up. It's always good to know what worked and what didn't.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 10, 2008 at 6:28 am
GilaMonster (12/9/2008)
Matt Miller (12/9/2008)
Funny - that's the EXACT reaction I got when I tossed it back....:)
Just about every time I've done a presentation or informal training and mentioned the problems...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 10, 2008 at 6:07 am
Sorry for the confusion. Thanks for the clarification Gail.
It's still the approach I'd take, but I'd sure take the time to examine those indexes.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 9, 2008 at 1:16 pm
That last query... the uh... you know it... well... uh...
Never mind. That actually makes my current local favorite look intelligent:
DECLARE @i int
SET @i =1
IF @i = 0
BEGIN...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 9, 2008 at 1:03 pm
Jeffrey Williams (12/9/2008)
Grant, I would not recommend issuing the above - especially since it is deprecated in SQL Server 2008. Here is the message you will get on a...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 9, 2008 at 12:51 pm
First things first, I think your statistics may be out of date. on [SWUS].[dbo].[SW_Ord_List_Ext].[_dta_index_SW_Ord_List_Ext_23_254064091__K3_1_4_5_18_20_22] [OLE]. The estimated number of rows is 54, the actual is 48000. That's a bit of...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 9, 2008 at 11:49 am
Not surprising. The function is basically running a query for each and every row in your database.
A better approach would be to JOIN to the lookup table, either directly or...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 9, 2008 at 11:39 am
In general, yes, you'll want to have multiple file groups. I'd recommend them for your OLTP system too. As to specifcally how many and where, that's hard to to say....
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 9, 2008 at 11:03 am
Instead of shrinking the database at the beginning of the process, I'd suggest growing the log out to the necessary size and making sure that it's cleaned out (BACKUP LOG...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 9, 2008 at 10:55 am
Do you have an execution plan showing how the function is behaving?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 9, 2008 at 10:53 am
That's great. I hadn't even tried it in 2005. Thanks for posting.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 9, 2008 at 10:51 am
Total agreement.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 9, 2008 at 7:57 am
Viewing 15 posts - 19,126 through 19,140 (of 22,226 total)