Viewing 15 posts - 6,166 through 6,180 (of 22,219 total)
You don't need this:
ALTER DATABASE MyDatabase
SET ALLOW_SNAPSHOT_ISOLATION ON
That's a different kind of snapshot isolation that is controlled by each connection and transaction. Read_Committed_Snapshot should be sufficient. You're probably best 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
May 6, 2015 at 3:52 am
Not to my knowledge. But then, I haven't had to use 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
May 6, 2015 at 3:49 am
Nice attempt at your first blog post.
Unfortunately, there are a few questionable suggestions in there.
For example, what's the difference between these two queries:
SELECT * FROM Sales.SalesOrderHeader AS soh
LEFT JOIN Sales.SalesOrderDetail...
"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
May 5, 2015 at 5:24 pm
I'd set up an extended event session and include causality tracking. I'll bet this is part of some extended transaction and just evidencing the deadlock in a funny way.
"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
May 5, 2015 at 5:10 pm
The Repeatable Read isolation level is much more restrictive, holding locks until a transaction is committed so that others cannot modify data, so yeah, that's absolutely going to lead 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
May 5, 2015 at 4:27 pm
That's weird. What's the isolation level on the connections do you know?
Sorry I don't have better info. This one looks really odd.
Nice job on the PR.
"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
May 5, 2015 at 10:56 am
Yeah, those discrepancies can make you nuts. I usually don't even attempt to resolve them and just say "This one is different than that one" and keep going. Makes my...
"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
May 5, 2015 at 10:11 am
Hey Jared!
I'm not sure. Are these statements part of a larger batch? Do you have triggers on the system? How about CDC or Audit? It seems like something other than...
"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
May 5, 2015 at 10:04 am
Unless you're operating in a development environment, I wouldn't suggest even using STATISTICS IO. I've actually noticed it negatively impacting queries. Instead I capture events using extended events (you can...
"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
May 5, 2015 at 9:55 am
When all inserts, updates and deletes return an error and the data being transmitted gets lost, most people consider that pretty dire.
"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
May 5, 2015 at 9:53 am
Ummmmm....
No.
NoSQL used to mean, no gol darned Ess Que Ell because we hate the DBAs and we hate the language and we just want to go FAST FAST FAST and...
"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
May 5, 2015 at 7:29 am
You absolutely can. Create a backup device and then backup to it. It can be a tape. But, understand, going directly to tape is much slower which could have all...
"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
May 5, 2015 at 7:06 am
You should set up domain accounts. That's the preferred mechanism of managing SQL Server anyway.
"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
May 5, 2015 at 7:03 am
Deadlocks are always about performance. The faster an update occurs, the less likelihood of deadlocks. So, first things first, make sure that your updates are performing well. Are they doing...
"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
May 5, 2015 at 7:02 am
it could be due to index fragmentation from updates or inserts within the cluster. Moving the data all at once leads to less fragmentation, which would explain the differences 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
May 5, 2015 at 6:43 am
Viewing 15 posts - 6,166 through 6,180 (of 22,219 total)