azuredatastudio
azuredatastudio copied to clipboard
microsoft
Database List Fails to Load
Issue Type: Bug
- Connect to Server with 5000 databases (Maximum allowed in Azure).
- Attempt to use Servers->Databases.
- Error will show "Object Exporer task didn't complete within 45 seconds"
I had already lengthened the timeout in the advance properties of the connection to 120 seconds, but to no avail. It doesn't seem like listing the DBs should take any appreciable amount of time unless it's trying to run some metadata queries on each one too.
Azure Data Studio version: azuredatastudio 1.3.1-insider (bd53e685d0091f9fe09c2662c30e0e506c402561, 2018-11-09T19:34:35.108Z) OS version: Windows_NT x64 10.0.17134
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2904) |
| 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: disabled_software rasterization: enabled video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled |
| Memory (System) | 31.85GB (12.49GB free) |
| Process Argv | C:\Program Files\Azure Data Studio\azuredatastudio.exe |
| Screen Reader | no |
| VM | 0% |
Any chance this is likely to make it into a near-term release? This is the only thing that really holds me back from using this great tool.
Same here using latest version 1.8.0
We "only" have 300 databases but I am also facing this issue with the default timeout of 45 seconds.
I have the same remark: could you perhaps quickly display all databases, then, eventually when required, fetch each database properties in background (on demand).
~~Getting the same issue after updating to 1.8.0~~
~~We have only 10 databases~~
Edit: I was getting "Object Exporer task didn't complete within 45 seconds" error, however login under a different user solved the problem
@g-rad are you getting the error "Object Exporer task didn't complete within 45 seconds" or is the list just failing to expand?
@kburtram I updated my comment. The issue was resolved by using a different db user, I guess it's something to do with permissions.
This persists for me on 1.10. Even on servers with only 300 databases it will time out. Oddly, the list of of databases in the Search Widget on the Server Dashboard loads them just fine. Even when there are 5k DBs. So it seems like the code that fetches the list of DBs in the Search widget is different than the code that fetches the list of databases in the Servers Pane.
I am also facing same issue with only 100 databases.. Please let me know if any solution for it
Moreover the "Search" area in the server details is able to list all databases quickly, but the Connections explorer does not.
I think you should at least try to use a lightweight query (using master db) to populate the nodes, then perform the long request on background, or only on demand for each node.
Same issue with less than 20 databases ! I'm using user token as authentication method and connecting to Azure SQL database server.
Is there any chance this issue can be raised further? It has been an issue for coming up to two years and has spanned many versions. It is not like this is an intermittent or isolated issue to a specific version. This is a chronic issue which happens constantly.
I have multiple Azure SQL Servers with varying numbers of databases from as few as 2 up to as much as 60. And this error appears for all.
Error and version details attached:
Still an issue. Please fix this it's really annoying. It makes every task and navigation much more complicated.
Yes, still an issue for me too.
Unfortunately turning it off and turning it back on doesn't fix this one 🙄
Please fix as it's a really annoying issue and it has been open for over two years.
Still an issue for a co-worker who has version 1.29.0 installed. His account can see all databases and objects in SSMS (everything works as you would expect there), but he cannot see them in his Connections window (under the databases folder).
This works for me when there are few databases on the server. But if there are more than 100 databases this times out for me and I can't browse the databases. If I create a query I can jump between the databases in the database dropdown fine. It's just that navigation in the Object Explorer that is not working. I'm using Azure Data Studio v. 1.33.1
Same issue, 3 years running now, times out even though there are only about 50 databases on the server.
Running a query and connecting immediately shows all the databases in the dropdown. Wish this would get some attention for once.
Well, I thought I'd just share the solution that has just worked for me 30 minutes ago when I faced the same exact issue.
Please fix this! I have to keep SSMS running just to use the object explorer!
Same error: "Object Exporer task didn't complete within 45 seconds"
Version: 1.39.1 (system setup) Commit: https://github.com/microsoft/azuredatastudio/commit/7553f799e175f471b7590302dd65c997b838b29b Date: 2022-08-30T01:11:13.047Z VS Code: 1.62.0 Electron: 13.6.6 Chrome: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.19043
Same issue for me,
Version: 1.39.1 (user setup) Commit: 7553f799e175f471b7590302dd65c997b838b29b Date: 2022-08-30T01:11:13.047Z VS Code: 1.62.0 Electron: 13.6.6 Chrome: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.22000
Issue is now fixed with https://github.com/microsoft/azuredatastudio/issues/21475 addressed. The latest insiders build contains fix, it will be available in the next stable release.
