Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. COI'm actually starting my queries from Visual Studio's Server Explorer window instead of via the SQL menu. I did just run a query from the SQL menu as you mention and it does in fact allow me to copy the column headers. I really prefer how the Server Explorer window automatically keeps all my server connections listed, and shows all the databases, tables, views, and stored procedures in a tree view underneath. Do you know of a way to display this type of tree view when doing queries via the SQL menu? If so, I would switch.
      singulars
    2. COUse the SQL editor the way I mentioned above. You can keep the server explorer pinned to the side to keep the view of servers and tables. To pin it to the side look at the top of the server explorer pane and you should see a pin icon. If it is facing down it will stay in place no matter what is in the main work area.
      singulars
    3. COYeah, I always keep the Server Explorer pinned. The way queries often start for me is...I will be looking at the data in a table (by having right-clicked the table name in Server Explorer and selecting "Show Table Data"), then I'll decide to join in some other data, so I'll display the SQL pane and start building away. This leaves me in the situation in my post (no way to export column headers). If there's any way to enable the "copy column headers" capability from queries started via the Server Explorer, that would be helpful for the way I currently work.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload