azure - Recovering from a possibly failed scale-up -
for purposes of familiarizing myself new azure sql tiers, cloned 7gb production database business standard s0 tier. operation worked without issue, creating ~3.5gb database (i guess skips index creation?). fired ssdt, added new publish script, , published. mistake, little s0 dtu utilization skyrocketed 100%. cancelled ssdt publish.
while ssdt publish (slowly) cancelling, scaled server s0 -> s2 see happen. 15 minutes after clicking scale button, ssdt publish (which still working on cancelling) forcibly disconnected. last 45 minutes, database has been reporting "scale operation in progress..." while showing 0 successful connections, 99.95% dtu percentage, , constant database size of 3.56gb.
my questions are:
is there way see status of scale operation beyond simple "scale operation in progress message?"
is there way abort operation, destructively or otherwise?
when running expensive operations (like creating 5gb of indexes), best practice scale enterprise tier, run operations, scale down normal tier?
when scaling, dashboard show resources used scaling process? meaning if see 99% dtu utilization after initiating scale, seeing resources being used scaling operation, or normal database activity only?
re #1: there percentage progress column in sys.dm_operation_status i'm not sure how accurate value scale operations. can query view master database.
re #2: there not. duration depending on size of database. other factors can play role. if have impression operation stuck, should file support ticked.
re #3: if chose higher performance level operation finish in less time. db able handle additional load better.
re #4: resources used scale operation not accounted included in utilization data see system operation.
Comments
Post a Comment