Viewing 15 posts - 6,496 through 6,510 (of 22,221 total)
Arjun SreeVastsva (4/1/2015)
I have tried to shirnk the database also below error I am getting
The transaction log for database 'New' is full due to 'AVAILABILITY_REPLICA'. (Microsoft SQL Server, 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
April 1, 2015 at 5:50 am
To begin to get an understanding of what is needed to help out, I'd like to suggest getting a copy of the book "Troubleshooting for the Accidental DBA." It's free...
"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
April 1, 2015 at 5:49 am
GilaMonster (4/1/2015)
Crystal ball to aisle 3 please. Crystal ball to aisle 3.http://www.sqlservercentral.com/Forums/Topic1673420-2572-1.aspx
Wow. "Here's a screen shot that says the same thing I already typed. That should clear up everything."
Frightening.
"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
April 1, 2015 at 5:46 am
Perry Whittle (4/1/2015)
Grant Fritchey (3/30/2015)
Although, ideally, you'd store them all in a central location so they're available immediately...
"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
April 1, 2015 at 4:18 am
A common table expression is just a derived table (except when we're talking about recursion). So you can just treat it as another table in the query:
WITH myCTE AS
(SELECT *...
"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 31, 2015 at 4:59 pm
Could you capture the execution plan? There's just too much to walk through there. If we can see what the optimizer is doing, it'll be easier.
"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 31, 2015 at 3:36 pm
Are all the properties on each of the operators in the plan exactly the same?
On a guess, I'd be inclined to suggest differences in the ANSI settings possibly causing differences...
"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 31, 2015 at 3:34 pm
I'm with Kevin. And the way around this is to try out the third party software on your own. Don't look to them for support. Test it and see if...
"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 31, 2015 at 12:06 pm
I'd suggest looking at the statistics in more detail, especially on the tables that are the biggest or that are called the most frequently. Get a sense of 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 31, 2015 at 12:03 pm
Steve Jones - SSC Editor (3/31/2015)
Grant Fritchey (3/31/2015)
I use semicolons on terminators for all my statements. Everyone should.
You do or Prompt does it for you?
Well, Prompt does it for me...
"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 31, 2015 at 11:18 am
stephen.long.1 (3/31/2015)
Regardless of the merits of adding semicolons at the end of all statements (something which I don't do, 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 31, 2015 at 8:10 am
Just not crazy about this phrasing:
Since few semicolons are used,
I use semicolons on terminators for all my statements. Everyone should.
"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 31, 2015 at 7:08 am
And when you think you have a handle on the changes suggested, all good, take a look at the execution plan to understand how the optimizer is resolving the query....
"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 31, 2015 at 7:06 am
What you can do is restore your database to another location and then run the full CHECKDB statement there. You really do need to do the internal logical checks as...
"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 31, 2015 at 7:04 am
You may just have a long running transaction. Check to see if that process is blocked by looking at sys.dm_exec_requests.
"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 31, 2015 at 7:02 am
Viewing 15 posts - 6,496 through 6,510 (of 22,221 total)