Azuredatastudio: BUG: SQL Operations Studio doesn't save result to Excel

Created on 15 Sep 2018  路  4Comments  路  Source: microsoft/azuredatastudio

  • SQL Operations Studio Version: 0.32.8
  • Operating system: Windows 10 Home x64

SQL Operations Studio doesn't save result to Excel. When I hit "Save", no file appears and no message pops up to indicate that file is created. I could manage to save file once per session. Now I tried 20 times to save file - and all is in vain. 馃槓 Can this bug be connected with previously fixed bug? 馃

Steps to Reproduce:

  1. Fire up new instance of SQL Operations Studio.
  2. Type in SELECT 1 and execute it.
  3. Save result to Excel.
Area - Query Editor Bug Needs More Info

Most helpful comment

It sounds like this may be the same bug as #2384 which is already fixed in our code but has only been released in insider builds (you can grab the latest insiders build at https://github.com/Microsoft/sqlopsstudio/releases/tag/0.33.5 if you want)

Does the workaround posted there of "in result set right-click, select-all, export as csv/json/excel" work for you?

All 4 comments

It sounds like this may be the same bug as #2384 which is already fixed in our code but has only been released in insider builds (you can grab the latest insiders build at https://github.com/Microsoft/sqlopsstudio/releases/tag/0.33.5 if you want)

Does the workaround posted there of "in result set right-click, select-all, export as csv/json/excel" work for you?

@MattIrv I came across this after getting set up on Ubuntu Desktop 18.04 using

Version 0.32.8
Commit efd470b3c771ef7473ba3cf108a33b6579c96a53
Date 2018-08-30T19:33:15.959Z
VS Code 1.23.1
Shell 1.7.16
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

I thought I had tried everything and couldn't get an export (to csv) work. The note you gave about explicitly right click > Export (as opposed to select all, and still trying to use the export buttons) worked for me just now.

@MattIrv Yes, this workaround does work. Thanks!

This should be fixed in the 0.32.9 release. Please reactive if the problem persists.

Was this page helpful?
0 / 5 - 0 ratings