Skip to content

Migrating from Azure Data Studio to polyglot pain points #4071

@therealkeys

Description

@therealkeys

Currently migrating my data science workload from Azure Data Studio to polyglot notebooks, as advised. I have the following grumbles.

  1. Not being able to manage MSSQL connections, having to import packages and input connection strings for each notebook is painful. (Similar with python, which although needed to be separate notebooks had a unified kernel manager)

  2. Not being able to preview data, sort and filter like what is possible in ADS

  3. Not being able to easily export save data from the preview such as in ADS (it was a button)

  4. Probably not a problem for here, but in ADS you could edit data in the table itself. Which was very useful for auxiliary tables

Describe the solution you'd like
I would like a unified kernel manager, that saves the connections.

I would also like the ability to sort/filter data views and display more rows with a scrolling feature such as in ADS (which was 5000 rows by default but could be configured for more).

I would like the ability to save data to csv/excel from SQL cells from a button on the data preview.

Could you point me where to take the data editing queries?

Describe alternatives you've considered
I've managed to take the data from a SQL cell across to a python cell, which displayed more of the returned data, but didn't allow for sorting/filtering or exporting

While this is all possible in pandas, these were incredibly useful features in ADS.

Ideally I'd like to use the data wrangler extension, but I believe because the python kernel is a sub kernel, data wrangler doesn't 'fire'

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions