What are different kernel options in Azure Data Studio Notebooks?
Among the many features of Azure Data Studio (ADS) is the feature to create Jupyter Notebooks. Jupyter Notebooks is a web application that allows users to create documents containing text, live code elements, query results, and images. Azure Data Studio notebooks offer several different
The programming language-specific processes running independently are called kernels.
Kernel options in Azure Data Studio
Different kernel options include:
- SQL Server
- PySpark
- Python 3
- Spark | Scala
- Spark | R
- PowerShell
where each Notebook supports only one kernel.
Besides the kernel options, there is the Attach to option, which provides the target context for the kernel. To provide context for the SQL Kernel, Attach to can be set to any SQL server or PostgreSQL server instances. For Python3 Kernel, we can attach to localhost, and so on.
What can you do with Azure Data Studio Notebook?
There are several use cases for the ADS Notebooks. Some of them are:
Saving diagnostic queries
We can save and share the diagnostic queries with colleagues. These queries might include query statistics, stored procedures statistics, waiters and blocking reports, etc. We can also save the diagnostic queries as a baseline and rerun them in the future to track changes.
Sharing the context
ADS Notebooks are a great way to share the context of different situations with others. As a Database Administrator, say you wanted to share the context of a blocking situation with someone. You would probably write an email mentioning which query you ran, where you ran it, and what the results were. With the Notebook, we can simply save it and share it with others to provide the context.
Exporting query results
Another use case of ADS Notebooks is that we can save and add the query results in presentations or simply share them with colleagues.
Creating Troubleshooting books
Database Administrators can combine their special scripts into notebooks and make them available to their IT departments. They can even create Troubleshooting books by combining the Notebooks.
Defining new deployments
We can define new deployments using Notebooks without the wizard experience. For example, for SQL server deployment in a container, we can get the code we need to do something, operationalize it within a notebook, and run it, instead of hiding anything behind a clickthrough wizard.
Free Resources