Viewing 15 posts - 3,496 through 3,510 (of 22,219 total)
Doggone it. The formatting is messing up. I've fixed it twice now. I get it right and posting it messes 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
November 28, 2017 at 12:02 pm
SELECT COUNT(1),
vb.Value
FROM Listings AS el
INNER JOIN Bindings AS vb
ON vb.fieldid = 7100
AND el.EntityID = vb.EntityID
WHERE...
"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
November 28, 2017 at 12:00 pm
Sounds like the backup may have been corrupted. Try restoring it to a different server. If it fails there too, that's the problem. You'll need a new backup. If it...
"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
November 28, 2017 at 11:56 am
It's possible that the optimizer will just change it to a join anyway. If you can, post the execution plans, preferably the actual plans.
"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
November 28, 2017 at 8:48 am
Could be several things. You have transactions that you're waiting on to complete before the database goes into single user. Alternatively, someone else connected ahead of you and you're waiting...
"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
November 28, 2017 at 8:46 am
roger.plowman - Tuesday, November 28, 2017 6:22 AMAnything from Red Gate
Well, you get no argument from me on this point.
"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
November 28, 2017 at 7:02 am
Plan affecting settings are stored inside the execution plans. However, everything else is through standard events like existing_connection. It lists a lot of stuff, but not the subnet failover setting.
"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
November 28, 2017 at 4:59 am
"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
November 28, 2017 at 4:30 am
I don't know because I don't use the tool but, if you need...
"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
November 27, 2017 at 8:12 am
"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
November 27, 2017 at 6:14 am
Yeah, you're on the right track. I've used AZCopy for exactly this type of operation with Azure SQL Data Warehouse. I used Azure Automation instead of Elastic Jobs. I'm 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
November 27, 2017 at 6:10 am
"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
November 26, 2017 at 2:07 pm
All these functions on your join criteria like this one are going to prevent index use and slow down performance: "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood" Author of:
- Theodore Roosevelt
SQL Server Execution Plans
SQL Server Query Performance Tuning
November 25, 2017 at 6:43 am
I agree with the previous answer. Group by functionality and purpose, not by technology. You might have a Testing resource group, for example, on which you run validations prior 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
November 24, 2017 at 1:22 pm
Unless you've set up and are using Azure Active directory, you're going to have a hard time automating this process from Azure. This is because it won't be able 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
November 24, 2017 at 1:20 pm
Viewing 15 posts - 3,496 through 3,510 (of 22,219 total)