Viewing 15 posts - 11,026 through 11,040 (of 22,219 total)
Simha24 (4/24/2012)
SELECT i.name AS IndexName,SUM(s.used_page_count) * 8 AS IndexSizeKB
FROM sys.dm_db_partition_stats AS s JOIN sys.indexes AS i ON s.[object_id] = i.[object_id] AND s.index_id =...
"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
April 24, 2012 at 8:57 am
Wait, partitioned?
Why not use the moving partition approach then? You don't delete anything. That's exactly what partitions are all about.
"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
April 24, 2012 at 8:00 am
How big are those indexes. If they're less than 8 pages in size, defragmenting might not work at all. I would suggest setting a low limit on defragmenting indexes. Somewhere...
"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
April 24, 2012 at 7:10 am
Based on that plan you're still doing a loop.
But, based on the plan, you're getting a table scan for each delete. The predicate is here: [MIS].[dbo].[LIV_CSS_DP_Counts].[day]=[@todelete]
That suggests that an index...
"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
April 24, 2012 at 7:08 am
The others are 100% correct. Nothing happens to those data types. But, to be sure what is going to happen to your databases when upgrading from 2000, you should run...
"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
April 24, 2012 at 6:08 am
It's like I said. An address table instead of fields in the person table. That way you can store a single address one time. Then an interim table, a table...
"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
April 24, 2012 at 6:01 am
I am not certified, so take my advice with a HUGE grain of salt...
Considering the differences between 2008 & 2012 and the fact that MS has changed the certifications and...
"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
April 24, 2012 at 4:56 am
It's basically OK. I'm not crazy about how you've set up the contacts relationship. I would have two different interim tables, one for relations between a person and an address...
"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
April 24, 2012 at 4:54 am
Thanks. Jumped right on that.
"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
April 24, 2012 at 4:49 am
The best way to track T-SQL commands that have been issued in the past is through an extended event session. They're easy to set up and there's a function to...
"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
April 24, 2012 at 4:46 am
Assuming that's an accurate representation of the query, you don't have a WHERE clause. That means you're processing everything in the table. You're not going to be able to improve...
"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
April 24, 2012 at 4:34 am
Now that you have a batched process, the right way to go, you need to worry about how the optimizer is handling it. Do you have an index on the...
"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
April 24, 2012 at 4:32 am
Lynn Pettis (4/23/2012)
Grant Fritchey (4/23/2012)
Lynn Pettis (4/23/2012)
Grant Fritchey (4/23/2012)
And I'm out.Oh well, you can't say I didn't try.
Well, we could say it, but we would be lying... 😉
I had...
"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
April 23, 2012 at 3:43 pm
Lynn Pettis (4/23/2012)
Grant Fritchey (4/23/2012)
And I'm out.Oh well, you can't say I didn't try.
Well, we could say it, but we would be lying... 😉
I had to show him one...
"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
April 23, 2012 at 2:57 pm
And I'm out.
Oh well, you can't say I didn't try.
"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
April 23, 2012 at 2:33 pm
Viewing 15 posts - 11,026 through 11,040 (of 22,219 total)