Viewing 15 posts - 4,516 through 4,530 (of 22,219 total)
It's only going to be one to one if the initial insert is inserting a single row at a time. You should then see it that way. However, if 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
August 23, 2016 at 8:55 am
You've got it pretty much nailed. It will do exactly what you're expecting of it. The only trick is that you need to do a point in time restore of...
"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
August 23, 2016 at 8:48 am
ChrisM@Work (8/23/2016)
"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
August 23, 2016 at 7:08 am
This is a seven year old thread, so I shouldn't comment on it, but I can't help but point out that both links in the last two posts which presume...
"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
August 23, 2016 at 6:23 am
Beatrix Kiddo (8/23/2016)
It's not supported in Azure yet.
I had to go and look. You're 100% correct and I stand corrected.
BTW, can't help but point it out, not only does SQL...
"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
August 23, 2016 at 6:02 am
Sharding is still a choice that you can do. Federations are gone for sure and certain.
"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
August 22, 2016 at 3:15 am
Which version of SSMS are you using? I'm pretty sure the Intellisense features in the 2016 SSMS work on Azure. Although, frankly, I don't like them that much. I really...
"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
August 22, 2016 at 3:14 am
GilaMonster (8/19/2016)
!!!!https://www.pluralsight.com/courses/identifying-fixing-performance-issues-caused-parameter-sniffing
And massive amount of work it was too. Recording's the easy part. Scripting is the most time consuming, editing probably the most difficult.
Congrats!
"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
August 19, 2016 at 10:49 am
BLOB_EATER (8/18/2016)
Grant Fritchey (8/18/2016)
Jeff Moden (8/18/2016)
It also names the stats in a fashion almost identical to how SQL Server does it
BWA-HA-HA!
I was just having a conversation about statistics 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
August 18, 2016 at 10:02 am
Jeff Moden (8/18/2016)
It also names the stats in a fashion almost identical to how SQL Server does it
BWA-HA-HA!
I was just having a conversation about statistics in India last week...
"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
August 18, 2016 at 8:36 am
Using extended events, you can capture all the connection information and suss out if there is any information that might lead to the individual user in that way. However, 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
August 18, 2016 at 7:55 am
Brandie, go home.
"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
August 18, 2016 at 7:53 am
ChrisM@Work (8/18/2016)
Brandie Tarvin (8/18/2016)
Brandie Tarvin (8/18/2016)
Ed Wagner (8/17/2016)
"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
August 18, 2016 at 5:34 am
It means that while inserts/updates/deletes are occurring, the processing necessary to add/modify that data in that index is causing blocking of other processes. That's all. Based on this, we don't...
"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
August 18, 2016 at 4:11 am
Yes to everything Gail says. Plus, we're not even addressing whether or not we need to worry about sample size or Full Scan on the statistics updates. Different statistics 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
August 18, 2016 at 3:59 am
Viewing 15 posts - 4,516 through 4,530 (of 22,219 total)