Viewing 15 posts - 6,016 through 6,030 (of 22,219 total)
Eric M Russell (5/27/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
May 27, 2015 at 11:13 am
Eric M Russell (5/27/2015)
Kyrilluk (5/27/2015)
Eric M Russell (5/26/2015)
Kyrilluk (5/26/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
May 27, 2015 at 10:43 am
Kyrilluk (5/26/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
May 27, 2015 at 10:35 am
Since this is two completely different statements, assuming we're putting this into a stored procedure, why not create two stored procedures? You're looking at the need for two different execution...
"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
May 27, 2015 at 7:56 am
If you can't get in with the DAC you may need to restart the service. Do it with the command lines -f and -m to get it to a minimal...
"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
May 27, 2015 at 7:21 am
Views that call to other views and nest and join on views is a notorious code smell that leads to poor performance. My suggestion, write the query you want directly...
"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
May 27, 2015 at 6:25 am
Sounds like there must have been some security changes on your server. The login you're using doesn't have permission to run the RESTORE command.
"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
May 27, 2015 at 6:22 am
There's no way to correlate what's stored in those DMVs to any query. So, instead, you need to query directly against the XML of the execution plans in order 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
May 27, 2015 at 6:22 am
Brandie Tarvin (5/27/2015)
Just curious how many people on The Thread are World Cup fans. Cause... STUFF and MORE STUFF.And I was wondering how y'all felt about it.
Damn! Still two more...
"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
May 27, 2015 at 6:17 am
GilaMonster (5/27/2015)
WhiteLotus (5/26/2015)
I don’t think eliminate distinct will make any difference ….By which you mean you've tested it and it didn't make any difference? ....
Despite the fact that the DISTINCT...
"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
May 27, 2015 at 4:30 am
I just ran a quick experiment with this code:
DECLARE @i INT = 0;
WHILE @i < 300
BEGIN
SELECT * FROM dbo.Agent AS a
SET @i += 1;
END
I was able to see all 300...
"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
May 26, 2015 at 9:58 am
I'm happy to help out any way I can.
Why were you trying to get 250 execution plans though? I'm just confused (not questioning 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
May 26, 2015 at 9:48 am
You're using SSMS to capture a batch (sounds like a WHILE or CURSOR?) that is executing over 250 statements and you're trying to capture all 250 execution plans? I wouldn't...
"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
May 26, 2015 at 7:17 am
If I'm understanding the question, you just need to use RESTORE ... WITH MOVE. There are samples at the link. Using WITH MOVE will allow you to rename the data...
"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
May 26, 2015 at 7:14 am
If you're returning 45,000 rows out of a 197,000 row table, That's approximately 25% of all the data in the table. The fastest way for it to perform that will...
"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
May 26, 2015 at 7:11 am
Viewing 15 posts - 6,016 through 6,030 (of 22,219 total)