Viewing 15 posts - 10,381 through 10,395 (of 22,219 total)
I've got a detailed blog post on what's going on here[/url]. As noted, you need to backup the log file. You can change the database to simple recovery 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
September 26, 2012 at 11:35 am
If the optimizer still thinks, based on statistics, a different index is more selective than your filtered index, that would explain why it's being selected. I can't say beyond 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
September 26, 2012 at 7:58 am
Yeah, we're comparing apples to hammers to a degree. If there are varying loads on the servers, other differing executables, etc., then you can't really compare resource usage between them.
"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
September 26, 2012 at 7:11 am
So, how's the material? You're reviewing more of the rough & ready aspect of getting the alpha, which is cool, but I'm curious how we did on the meat.
"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
September 26, 2012 at 7:09 am
For those interested, it's worth mentioning that Red Gate SQL Backup[/url] has an automation routine built into the newest release that makes backup testing a lot easier. It will do...
"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
September 26, 2012 at 4:25 am
It does depend on how you defined "used". You could also take a look at the index usage statistics to see how often a clustered index (which is 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
September 26, 2012 at 4:04 am
You can check the ring buffers for one of three different error messages, Out of Memory messages, Low Physical memory or Low Virtual memory. You can also use the DBCC...
"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
September 26, 2012 at 3:49 am
It's a giant topic. But, as with everything else SQL Server, start with the Books Online. Microsoft Developers Network (MSDN) also has an example of a plan. And finally 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
September 26, 2012 at 3:46 am
It's limited based on the available memory.
But why would you be nesting IF/ELSE statements to the limit of your memory capacity? It strikes me that you might be going down...
"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
September 26, 2012 at 3:37 am
Creating a clustered index is generally considered to be part of the work of designing a database. Who designs a database? There's no absolute, hard and fast rule 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
September 26, 2012 at 3:26 am
SQL Kiwi (9/25/2012)
Grant Fritchey (9/25/2012)
I'm not getting what this guy is after, so I'm clearly not helping. Could someone else check it out please?
I tried my best, but it is...
"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
September 25, 2012 at 10:22 am
SQLSACT (9/25/2012)
Grant Fritchey (9/25/2012)
Yep. By design. Here's some description of it. Yet another reason to avoid auto_close.
Ok, so I'm definately going to change the option to false.
Question is, if I...
"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
September 25, 2012 at 6:43 am
anthony.green (9/25/2012)
"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
September 25, 2012 at 6:35 am
Yep. By design. Here's some description of it. Yet another reason to avoid auto_close.
"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
September 25, 2012 at 6:34 am
I'm not getting what this guy is after, so I'm clearly not helping. Could someone else check it out please?
Oh, and don't pile on the poor guy. I just mean...
"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
September 25, 2012 at 6:32 am
Viewing 15 posts - 10,381 through 10,395 (of 22,219 total)