Viewing 15 posts - 6,601 through 6,615 (of 22,219 total)
I can give an example of a "routine" shrink, but it's not on a production box.
We would take our production database and restore it to a staging machine. There, we'd...
"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
March 11, 2015 at 12:53 pm
Here's an article[/url] I wrote on the various mechanisms and what each one does for you. The best is what Gail says, restore the database.
"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
March 11, 2015 at 12:11 pm
It's probably the load on the server, the queries, the database design, the statistics, the indexes, etc., that are leading to high CPU use.
I'm with Gail, patch the server,yes. But...
"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
March 11, 2015 at 8:06 am
If you are going to try to capture events on a 24/7 basis, you might want to use extended events instead of trace. They have less impact on the server....
"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
March 11, 2015 at 7:02 am
I just did a quick couple of searches on Simple-Talk, and I don't see any. I've bugged the editors to get you one. In the mean time, understanding how the...
"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
March 11, 2015 at 4:40 am
The fragmentation problem of database shrink events is not to the indexes. That type of fragmentation is easily fixed. It's fragmentation of the file on disk. That's different and not...
"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
March 10, 2015 at 7:42 pm
I've not seen a 2014 BPA. According to this thread on MSDN, no, the 2012 version won't work.
"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
March 10, 2015 at 2:36 pm
xsevensinzx (3/10/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
March 10, 2015 at 11:51 am
A transaction can still be open for a sleeping connection. So, while it's not actively running anything, if it's still an open transaction, it's still holding locks.
"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
March 10, 2015 at 10:07 am
If it's doing 3 reads based on an index seek but taking 3 minutes, something else is going on. I'd look to see what the wait statistics look like around...
"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
March 10, 2015 at 8:05 am
The blocking makes sense. The types of locks that the query is attempting to take out don't allow for sharing with others. So, it has to wait until the first...
"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
March 10, 2015 at 7:52 am
Koen Verbeeck (3/10/2015)
Grant Fritchey (3/10/2015)
Koen Verbeeck (3/10/2015)
Grant Fritchey (3/10/2015)
... Then move on to my books.Subtle. :Whistling: 😀
I keep updating them for a reason.
The private jet doesn't pay for itself, right...
"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
March 10, 2015 at 7:49 am
Koen Verbeeck (3/10/2015)
Grant Fritchey (3/10/2015)
... Then move on to my books.Subtle. :Whistling: 😀
I keep updating them for a reason.
"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
March 10, 2015 at 7:16 am
I'm with everyone else, using NOLOCK is actually quite dangerous, mostly due to the ability to get duplicate or missing rows, which, as far as I know, most businesses absolutely...
"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
March 10, 2015 at 7:05 am
It sure sounds like you need to do fundamental query tuning, indexing, statistics maintenance, etc. Assuming you can't get someone in to help you who has experience with all this,...
"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
March 10, 2015 at 6:59 am
Viewing 15 posts - 6,601 through 6,615 (of 22,219 total)