Viewing 15 posts - 6,526 through 6,540 (of 22,229 total)
No, the data gets updated AND the log gets written. As was stated above, this is to help maintain ACID properties and it makes it possible to do point 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
March 30, 2015 at 2:59 pm
But if you're not using differentials, you can use the secondaries for backups. Also, the log backups can, roughly, be taken anywhere and then combined later. I wrote a chapter...
"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 30, 2015 at 2:56 pm
I have not done the 2005 SP4 upgrade to 2014, but, if the documentation says it supports it, it probably does.
I'd go with the first setup you have suggested there....
"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 30, 2015 at 10:49 am
I am just not sure. I'm not seeing indications for why it's going wrong. Double check that the constraint has the WITH CHECK option in 2014. Other than that... I...
"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 30, 2015 at 8:41 am
That doesn't mean it will lock the entire table (unless you're deleting a pretty substantial portion of it, but that's part of why you break it into smaller batches). 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
March 30, 2015 at 8:36 am
Breaking it into pieces and making sure that the delete statements are using indexes instead of scanning, those are really your choices if you can't partition 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 30, 2015 at 6:50 am
If you don't have any sort of auditing set up on your server, you won't be able to see who deleted data. You can set up Audit within SQL 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 30, 2015 at 6:49 am
Wish I could come over and play with this. The check constraint should allow the optimizer to eliminate servers from the choice. The fact that security might have changed 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 30, 2015 at 6:43 am
Alan.B (3/26/2015)
Alvin Ramard (3/26/2015)
Grant Fritchey (3/26/2015)
Piling on....
Now, multi-statement, table-valued, user-defined functions on the other hand, those things are all things evil.
You mean in a trigger? 😀
I suspect he meant...
"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 27, 2015 at 6:19 am
Piling on.
Triggers are not bad. They just have a hidden behavior that, when they're written poorly, can lead to lots of issues and long troubleshooting sessions. Use appropriately, they're fine.
Now,...
"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 26, 2015 at 3:42 pm
Yep. 100% by design. Isn't the optimizer the coolest thing ever.
"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 26, 2015 at 3:40 pm
Drenlin (3/26/2015)
Phil Parkin (3/26/2015)That's exactly what the compatibility level is for, though it does come with downsides: all of the new features in 2014 are turned off for the databases...
"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 26, 2015 at 3:30 pm
Yet Another DBA (3/26/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 26, 2015 at 3:26 pm
I agree with everything that Gail said.
Well, except that you ought to be using extended events instead of trace.
But yeah, you may be hitting waits, CXPacket waits are not, 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
March 26, 2015 at 3:18 pm
The index DMV, sys.dm_db_index_physical_stats, could cause blocking if you're asking for a detailed report. It's very intrusive.
I haven't seen or or heard about other DMVs causing blocking, yet.
"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 26, 2015 at 5:30 am
Viewing 15 posts - 6,526 through 6,540 (of 22,229 total)