Viewing 15 posts - 8,911 through 8,925 (of 22,224 total)
It's all about speed. When you need really fast OLTP processing, you go with the in-memory tables and the compiled procedures. The limitations are too severe for any small 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
February 15, 2014 at 4:03 am
Michael Valentine Jones (2/14/2014)
Luis Cazares (2/14/2014)
Michael Valentine Jones (2/13/2014)
3. The database is "overnormalized".That can be true (even if it usually isn't).
I am not sure what "overnormalized" even means, but anytime...
"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
February 15, 2014 at 3:40 am
Yeah, it could, although you might be better off creating the index on the table after you load 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
February 14, 2014 at 7:00 am
It sure sounds to me like the query could be tuned, but as to the long running stuff, I'd assume contention on resources. While it's running, have you collected wait...
"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
February 14, 2014 at 6:00 am
Everything Kevin said, then check out the execution plan to understand where the indexes are getting used and where they aren't. Just tossing them vaguely towards a query never works...
"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
February 14, 2014 at 4:40 am
This stuff is likely killing your performance too. It can't use indexes
DATEPART(dw, d.GREGORIANDATE) <> 1 AND DATEPART(dw, d.GREGORIANDATE) <> 7'
"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
February 14, 2014 at 4:37 am
I've done this using both T-SQL and PowerShell, but the trick is, you have to be able to set up access to a common location. If you can't do 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
February 14, 2014 at 4:32 am
Generally, this is when you go to your backups and restore the database to a point in time prior to the 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
February 14, 2014 at 4:28 am
Evil Kraig F (2/13/2014)
My understanding was the short circuit capabilities of the CASE statement would improve performance, but in a limited variety.
Instead of a simple data change on the 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
February 13, 2014 at 12:25 pm
Recompile will override, yes. You can't really see query hints through the execution plan. You can see them in the SQL text that is stored with the plan.
"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
February 13, 2014 at 9:13 am
OCTom (2/13/2014)
FKs make my job so much easier. I don't have to write the code that prevents orphaned...
"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
February 13, 2014 at 8:46 am
Idera's product works. But it will cause hits to i/o and you will have to have storage available for it, although not initially.
"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
February 13, 2014 at 8:23 am
Cool question and kind of fun. I tested it out this way:
IF (SELECT OBJECT_ID('Test1')
) IS NOT NULL
DROP TABLE dbo.Test1;
GO
CREATE 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
February 13, 2014 at 8:19 am
For just queries... I'd suggest going with Solarwindows (formerly Confio) Ignite. That's one of the best third party tools for just going after query performance. It's not so good with...
"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
February 13, 2014 at 8:05 am
Also, check the cost threshold for parallelism on the server. The default value is 5 and that is radically low for most systems. Changing that to an appropriate value (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
February 13, 2014 at 8:03 am
Viewing 15 posts - 8,911 through 8,925 (of 22,224 total)