Reputation
397
Next privilege 500 Rep.
Access review queues
Badges
2 10
Impact
~9k people reached

  • 0 posts edited
  • 0 helpful flags
  • 136 votes cast
Oct
6
comment How do I prevent a massive SELECT from blocking other statements?
@MarkWilkinson Well, nothing interesting, just a heavy SELECT which was likely causing either a table scan or gazillion of index seeks. The problem was resolved by creating a suitable index. Looks like something is seriously wrong with SQL Azure performance tiers.
Sep
25
comment How do I prevent a massive SELECT from blocking other statements?
@jkavalik That would be a speculation, not a real plan.
Sep
25
comment How do I prevent a massive SELECT from blocking other statements?
@MarkSinkinson I guess I can but that surely requires quite a lot of effort and time.
Sep
25
comment How do I prevent a massive SELECT from blocking other statements?
@MarkSinkinson I cannot even obtain an execution plan anymore because that requires running the query and disrupting production.
Sep
25
asked How do I prevent a massive SELECT from blocking other statements?
Sep
21
comment Why would CREATE INDEX with “online” mode suddenly slow my database down?
Why would this not happen earlier and what do I do to overcome it?
Sep
21
comment Why would CREATE INDEX with “online” mode suddenly slow my database down?
@SQLmojoe I added that into the question. The problem occurs both when creating an identical index and a non-identical index.
Sep
21
comment Why would CREATE INDEX with “online” mode suddenly slow my database down?
@JoshSimar The slowdown starts immediately once the statement start running.
Sep
21
revised Why would CREATE INDEX with “online” mode suddenly slow my database down?
added 273 characters in body
Sep
16
asked Why would CREATE INDEX with “online” mode suddenly slow my database down?
Aug
18
awarded  Nice Question
Aug
17
asked Why does my WHERE clause benefit from an “included” column?
Aug
10
asked Is unique index combined with a “not null” constraint equivalent to a PK constraint?
Aug
6
accepted Why does PK constraint require a separate index when I already have a suitable unique clustered index?
Aug
4
comment Why does PK constraint require a separate index when I already have a suitable unique clustered index?
@MikaelEriksson I'm not sure I won't break anything. I'd rather have PK changed to use the clustered index if that's possible.
Aug
4
comment Why does PK constraint require a separate index when I already have a suitable unique clustered index?
@ypercube Maybe it's possible with on-prem server, but surely not with SQL Azure.
Aug
4
comment Why does PK constraint require a separate index when I already have a suitable unique clustered index?
@a_horse_with_no_name I have an existing table and so I cannot just drop the clustered index - the index stores my table.
Aug
4
comment Why does PK constraint require a separate index when I already have a suitable unique clustered index?
@a_horse_with_no_name This is legacy, that's why. Is it possible to tell SQL Server to use the existing clustered index for the PK constraint perhaps?
Aug
4
asked Why does PK constraint require a separate index when I already have a suitable unique clustered index?
Aug
3
asked Why is DistinctSort followed by TopNSort in my query plan?