Viewing 15 posts - 5,806 through 5,820 (of 22,219 total)
The differences between the servers could be the amount of memory on the servers, the number and speed of the CPU, or just the load because resource contention on any...
"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
July 31, 2015 at 5:01 am
Partitioning very rarely helps performance within an OLTP situation. However, if you are looking at a situation where you're rolling off old data, partitioning becomes a pretty viable approach, in...
"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
July 31, 2015 at 4:58 am
Ah, it wasn't clear in the first post this is all dynamic SQL.
Try wrapping this in a transaction
exec sp_executesql @s
"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
July 31, 2015 at 4:11 am
Brandie Tarvin (7/30/2015)
SQLRNNR (7/30/2015)
Brandie Tarvin (7/30/2015)
And on another subject...I HAVE GUMMY BEARS! (fear me)
That can be taken multiple ways.
Let's guess that means this instead of the surgical process.
https://www.youtube.com/watch?v=mLpNGp-IFIk
edit: better link
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
July 30, 2015 at 12:28 pm
TheSQLGuru (7/30/2015)
4) A minor correction to what Grant said: the leading percent won't prevent index use. It will just prevent index SEEKs.
Very true and worth noting.
A pretty hefty percentage 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
July 30, 2015 at 12:27 pm
Pretty much the same stuff you'd capture if you were monitoring production servers. You want all the wait statistics. You want to see the queues, if any. You definitely should...
"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
July 30, 2015 at 10:01 am
The DISTINCT operation is going perform aggregation. You really shouldn't need it if your data structures are correct. That's a pretty big performance hit right there.
"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
July 30, 2015 at 9:58 am
SQLRNNR (7/30/2015)
Grant Fritchey (7/30/2015)
Brandie Tarvin (7/30/2015)
"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
July 30, 2015 at 8:51 am
Brandie Tarvin (7/30/2015)
"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
July 30, 2015 at 8:04 am
Brandie Tarvin (7/30/2015)
Work...
"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
July 30, 2015 at 6:09 am
Yeah, you should check out Minion Reindex[/url]. It's part of the MinionWare suite[/url]. It's a free piece of software and is quite excellent. I wrote up a review of 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
July 30, 2015 at 4:37 am
Do a LIKE search where you have wild cards on the starting side of the predicate
LIKE '%a1'
Is going to cause scans and prevent index use. I would strongly advise attacking...
"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
July 30, 2015 at 4:35 am
I'm seeing two different MERGE commands, no CTEs in sight.
"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
July 30, 2015 at 4:30 am
Here's an article[/url] I wrote on how to deal with versioned data. One of these solutions should work well for you.
"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
July 30, 2015 at 4:28 am
You can create the view using WITH SCHEMABINDING. That will prevent the table from being modified. Here's the CREATE VIEW syntax.
"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
July 30, 2015 at 4:27 am
Viewing 15 posts - 5,806 through 5,820 (of 22,219 total)