You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps to reproduce:
1-Connect to an Azure SQL Database server, using a connection that previously worked as expected
2-Verify the connection is established by successfully querying the db.
3-Observe the database under Servers in the Connections tab and see that once the connection is made (green dot), there is a loading symbol that never stops.
Expected behavior: Once the connection is made, the loading symbol should go away, and you should be able to expand the database to see the objects.
Azure Data Studio version: azuredatastudio 1.49.1 (2f696aa, 2024-08-13T18:12:38.831Z)
OS version: Windows_NT x64 10.0.19045
Restricted Mode: No
Preview Features: Enabled
Modes:
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz (8 x 2395)
Type: Bug
Steps to reproduce:
1-Connect to an Azure SQL Database server, using a connection that previously worked as expected
2-Verify the connection is established by successfully querying the db.
3-Observe the database under Servers in the Connections tab and see that once the connection is made (green dot), there is a loading symbol that never stops.
Expected behavior: Once the connection is made, the loading symbol should go away, and you should be able to expand the database to see the objects.
Azure Data Studio version: azuredatastudio 1.49.1 (2f696aa, 2024-08-13T18:12:38.831Z)
OS version: Windows_NT x64 10.0.19045
Restricted Mode: No
Preview Features: Enabled
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: unavailable_off
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Extensions (1)
The text was updated successfully, but these errors were encountered: