Viewing 15 posts - 1,891 through 1,905 (of 22,227 total)
It's the insert and update that are locking the table.
You can ignore these locks by using the nolock hint:
select count(*)
from mytable with (nolock)
BUT!!!
Know...
"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, 2020 at 2:02 pm
Execution plans, run times, I/O, data, data, data. You can't simply say IN good, NOT IN bad without data. You also can't say NOT IN good, IN bad without 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
March 10, 2020 at 11:18 am
I'm with Jeff. Pick and choose which of these indexes you drop & recreate. There are many, many tests out there that show inserting into a clustered table can be...
"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, 2020 at 11:15 am
I'd suggest next time you run a blocking report to understand why it's blocking. SELECT COUNT(*) has to do a scan, either of the table or an index. It's counting...
"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, 2020 at 11:05 am
Running out of support software is a serious business risk. I'd focus on that above anything else. I know this stuff comes with a price tag, but talk to 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 9, 2020 at 1:31 pm
Take a look at the execution plans when it's compiling in each compatibility mode to understand how the behavior is changing.
"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 9, 2020 at 11:49 am
You're trying to do an in-place upgrade? This is the installation software that is generating these errors? I'm unclear precisely what's happening.
Also, whatever you do, avoid updating to 2014. It's...
"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 9, 2020 at 11:47 am
Without seeing the code, it's hard to know for sure if this is the best way to get things done. It is possible within T-SQL to reference a data set...
"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 9, 2020 at 11:42 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
March 5, 2020 at 8:05 am
Well, that's the answer to your questions.
"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 5, 2020 at 8:01 am
Without data, we're talking nothing but guesses, and vague bad guesses at that. Go and turn on monitoring on the server. Set up Query Store. Enable an Extended Events session....
"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 5, 2020 at 4:33 am
The answer to both questions is Extended Events. That's what it's there for. Why would you NOT use it?
There is SQL Server Audit for the logins (not query calls),...
"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 3, 2020 at 10:01 am
Without more information, it's hard to say. An INSERT requires exclusive access while a SELECT can used shared access, or, if you have it enabled, snapshot copies of 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
March 3, 2020 at 9:58 am
one specific object common.
We have Object A which is common in some database, will have to retrieve the current row of Object A in all databases and insert 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 3, 2020 at 9:35 am
CHECKDB is actually a series of commands. Just break down the commands and do them separately. The documentation is online and elsewhere.
Your prod and non-prod databases have to be...
"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 3, 2020 at 9:33 am
Viewing 15 posts - 1,891 through 1,905 (of 22,227 total)