Viewing 15 posts - 7,786 through 7,800 (of 22,219 total)
Where the heck did I see it was 8gb? Maybe time to up my coffee intake. Sorry for the misunderstanding there.
The rest of the processing bit is still correct. You're...
"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 9, 2014 at 4:28 am
While I'm not a fan of GUIDs as clustered keys, I've seen it in a production system and it wasn't the end of the world. We did have to deal...
"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 8, 2014 at 8:30 am
So you're going to an underpowered machine (8gb is half the memory my laptop has) and you're running a very large aggregation query and returning 1.7 million rows. The machine...
"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 8, 2014 at 8:17 am
I agree with everything Sean said. I'll add to it by questioning the nonclustered indexes that you want to add. Why are you adding those. Do you know you need...
"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 8, 2014 at 8:08 am
SQLRNNR (7/8/2014)
Jeff Moden (7/8/2014)
The first day was spent filling out paper work and peeing in a cup." 😉Was that also a failure?:w00t:
Depending on my mood and the attitude 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 8, 2014 at 7:53 am
For really tiny databases like this (and 7gb is tiny) I wouldn't bother with differentials. A full backup will run very fast and a full restore will run very fast....
"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 8, 2014 at 6:41 am
Side note: But never use the Profiler GUI against a production system. Always use trace events to capture the information. Profiler is only used to consume the data after 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 8, 2014 at 6:38 am
And you can see if there's an index you can create that may help with the sort operation. It doesn't always work, but it's a possibility.
"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 8, 2014 at 6:36 am
Also check the default ANSI settings between your local SSMS and the remote SSMS. Differences there can result in different execution plans.
How big are these queries. 30 seconds for 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
July 8, 2014 at 6:35 am
What is it that you're actually looking for? Are you hitting a performance problem?
"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 8, 2014 at 6:32 am
Jeff Moden (7/7/2014)
"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 8, 2014 at 4:40 am
Most of the functions are the same with 6-8 joins or one. Most of the rules are the same dealing with a few rows or a few million. The real...
"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 7, 2014 at 10:04 am
If you're really going to be building a lot of databases, I'd suggest reading Louis Davidson's book. It's a great way to learn how to do database design.
"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 7, 2014 at 9:56 am
After you restructure it as was suggested already, this needs to be addressed:
(RTRIM(pc.CODE))
That will lead to scans which will seriously hurt performance. You shouldn't have functions on columns like...
"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 7, 2014 at 8:54 am
You can. I haven't done it myself, so I can't offer advice. But it's absolutely doable.
"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 7, 2014 at 8:30 am
Viewing 15 posts - 7,786 through 7,800 (of 22,219 total)