Issue Type: Bug
It does not seem that listing the DBs should take any significant amount of time unless it also attempts to run some metadata queries on each DB.
Azure Data Studio version: Azure Data Studio 1.6.0 (eb35dae1d1238e03f1cab3bd45e151f381b22aef, 2019-04-17T06:14:17.039Z)
OS version: Darwin x64 18.5.0
System Info
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)|
|GPU Status|2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled|
|Load (avg)|2, 2, 2|
|Memory (System)|16.00GB (10.68GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
Extensions: none
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:
@mayurrumal1 are there any relevant details regarding the server you're connecting to? e.g. is it a Azure SQL DB with low DTU, is the server generally responsive otherwise, etc?.
@mayurrumal1 are there any relevant details regarding the server you're connecting to? e.g. is it a Azure SQL DB with low DTU, is the server generally responsive otherwise, etc?.
I am getting this issue as well. And it's not just on small databases and elastic pools, but even ones with 20 vcores, and pretty much zero traffic going to them.
This looks like a bug within the application