Viewing 15 posts - 7,951 through 7,965 (of 22,224 total)
SQLRNNR (6/17/2014)
Eirikur Eiriksson (6/17/2014)
Sean Lange (6/17/2014)
SQLRNNR (6/17/2014)
My active threads has been missing most of the day. For...
"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
June 17, 2014 at 12:21 pm
No special issues associated with it. Each index can have it's own fill factor and it doesn't directly affect other indexes around it. It just affects storage and retrieval 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
June 17, 2014 at 12:18 pm
Hard to say based on the information at hand. For most databases less than 200gb, I had everything in primary and it all worked well enough.
"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
June 17, 2014 at 12:17 pm
Gazareth (6/17/2014)
Welsh Corgi (6/17/2014)
I found the following article that state that you should a good backup before you Kill the process.
I think what Russell meant there was make sure 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
June 17, 2014 at 12:16 pm
It almost has to be incorrect security on the instance. It might incorrect security on the server. But it has to be incorrect security.
"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
June 17, 2014 at 12:14 pm
I would suggest completely reconfiguring and reinstalling the system from scratch. I'd even nuke the operating system and start over. You don't want to deal long term with any kind...
"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
June 17, 2014 at 12:13 pm
I'd start any upgrade with the Microsoft SQL Server Upgrade Advisor. You want to know if you've run into issues with that before you do anything else. TechNet has 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
June 17, 2014 at 12:10 pm
ben.brugman (6/17/2014)
Grant Fritchey (6/16/2014)
If filtering on tableA is what you needed, just do that. The INNER JOIN will take care of the rest.
Thanks for you response, offcourse this was 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
June 17, 2014 at 10:07 am
You could be seeing something of what you're talking about, but as the data changes, if you have auto update stats turned on, you should see the stats change, although,...
"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
June 17, 2014 at 10:00 am
Two guesses, possibly out of date statistics on the tables in question or possibly something up with your I/O sub-system since you're seeing an I/O error.
EDIT
Sorry for the duplicate post....
"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
June 17, 2014 at 8:32 am
Two guesses, possibly out of date statistics on the tables in question or possibly something up with your I/O sub-system since you're seeing an I/O error.
"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
June 17, 2014 at 8:32 am
So if you don't have enough log space to do the delete in a single step, break it up.
"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
June 17, 2014 at 8:29 am
Maybe the statistics are out of date on the QA server leading to different execution plans? I know, truncating tables & all, but... Or, maybe statistics have changed sufficiently 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
June 17, 2014 at 8:28 am
There are a fairly large number of performance measures. The best documentation I have on that is in my book on query tuning. There's a link below. It also covers...
"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
June 17, 2014 at 6:11 am
Koen Verbeeck (6/16/2014)
Sean Lange (6/16/2014)
Koen Verbeeck (6/16/2014)
Evil Kraig F (6/16/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
June 16, 2014 at 3:26 pm
Viewing 15 posts - 7,951 through 7,965 (of 22,224 total)