-
Notifications
You must be signed in to change notification settings - Fork 904
Microsoft Ready 2019 Lab
During the Microsoft Ready lab you will be following these instructions on your own device. Open a browser on your device for these instructions, and not inside the actual VM. We will be copy/pasting snippets from this lab to inside the VM.
Welcome to Microsoft Ready! In this session, you will learn to build your own extensions for Azure Data Studio. Azure Data Studio is a data management tool that enables you to work with SQL Server, Azure SQL DB and SQL DW from Windows, macOS and Linux. In addition to providing core functionality like a rich T-SQL editing experience, we also provide an Extension Marketplace where the community can contribute their own Extensions so that anyone can use the extension.
These extensions are generally lighted up through our Dashboard, where users can quickly monitor and troubleshoot their databases.
Users can build their own Insight Widgets as shown in the image above, which are powered by T-SQL queries. This allows a user to see a visualization of the common queries they run day to day.
Over the course of this session, you will:
- Build your first Azure Data Studio extension using a Visual Studio Code environment.
- Use an Extension generator to help write an extension
- Create an Insight Widget extension
All prerequisites are already install on machine. As a summary, here is what is pre-installed:
- Azure Data Studio
- Visual Studio Code
- Git
-
Node.JS,
>= 8.9.1, < 9.0.0
- Yarn, follow the installation guide
- Python, at least version 2.7 (version 3 is not supported)
-
Yeoman,
npm install -g yo
-
Generator-sqlops,
npm install -g generator-sqlops
- SQL Server 2017 developer edition
- Visual Studio Code extensions
- SQL Operations Studio debug
- mssql extension
- Debugger for Chrome
- npm packages
- npm install -g vsce
-
Open Azure Data Studio.
-
Click new connection.
-
Select Localhost from Saved Locations and click Connect.
-
Click arrow next to localhost under Servers, then click arrow by databases, then right click WideWorldImporters and click New Query
-
Copy and paste this snippet
------------------------------Data file size---------------------------- declare @dbsize table (Dbname nvarchar(128), file_Size_MB decimal(20,2)default (0), Space_Used_MB decimal(20,2)default (0), Free_Space_MB decimal(20,2) default (0)) insert into @dbsize (Dbname,file_Size_MB,Space_Used_MB,Free_Space_MB) exec sp_MSforeachdb 'use [?]; select DB_NAME() AS DbName, sum(size)/128.0 AS File_Size_MB, sum(CAST(FILEPROPERTY(name, ''SpaceUsed'') AS INT))/128.0 as Space_Used_MB, SUM( size)/128.0 - sum(CAST(FILEPROPERTY(name,''SpaceUsed'') AS INT))/128.0 AS Free_Space_MB from sys.database_files where type=0 group by type' -------------------log size-------------------------------------- declare @logsize table (Dbname nvarchar(128), Log_File_Size_MB decimal(20,2)default (0), log_Space_Used_MB decimal(20,2)default (0), log_Free_Space_MB decimal(20,2)default (0)) insert into @logsize (Dbname,Log_File_Size_MB,log_Space_Used_MB,log_Free_Space_MB) exec sp_MSforeachdb 'use [?]; select DB_NAME() AS DbName, sum(size)/128.0 AS Log_File_Size_MB, sum(CAST(FILEPROPERTY(name, ''SpaceUsed'') AS INT))/128.0 as log_Space_Used_MB, SUM( size)/128.0 - sum(CAST(FILEPROPERTY(name,''SpaceUsed'') AS INT))/128.0 AS log_Free_Space_MB from sys.database_files where type=1 group by type' --------------------------------database free size declare @dbfreesize table (name nvarchar(128), database_size varchar(50), Freespace varchar(50)default (0.00)) insert into @dbfreesize (name,database_size,Freespace) exec sp_MSforeachdb 'use [?];SELECT database_name = db_name() ,database_size = ltrim(str((convert(DECIMAL(15, 2), dbsize) + convert(DECIMAL(15, 2), logsize)) * 8192 / 1048576, 15, 2) + ''MB'') ,''unallocated space'' = ltrim(str(( CASE WHEN dbsize >= reservedpages THEN (convert(DECIMAL(15, 2), dbsize) - convert(DECIMAL(15, 2), reservedpages)) * 8192 / 1048576 ELSE 0 END ), 15, 2) + '' MB'') FROM ( SELECT dbsize = sum(convert(BIGINT, CASE WHEN type = 0 THEN size ELSE 0 END)) ,logsize = sum(convert(BIGINT, CASE WHEN type <> 0 THEN size ELSE 0 END)) FROM sys.database_files ) AS files ,( SELECT reservedpages = sum(a.total_pages) ,usedpages = sum(a.used_pages) ,pages = sum(CASE WHEN it.internal_type IN ( 202 ,204 ,211 ,212 ,213 ,214 ,215 ,216 ) THEN 0 WHEN a.type <> 1 THEN a.used_pages WHEN p.index_id < 2 THEN a.data_pages ELSE 0 END) FROM sys.partitions p INNER JOIN sys.allocation_units a ON p.partition_id = a.container_id LEFT JOIN sys.internal_tables it ON p.object_id = it.object_id ) AS partitions' ----------------------------------- select TOP 10 d.Dbname, --(file_size_mb + log_file_size_mb) as DBsize, --d.file_Size_MB, d.Space_Used_MB, --d.Free_Space_MB, --l.Log_File_Size_MB, l.log_Space_Used_MB--, --l.log_Free_Space_MB, --fs.Freespace as DB_Freespace from @dbsize d join @logsize l on d.Dbname=l.Dbname join @dbfreesize fs on d.Dbname=fs.name order by d.Space_Used_MB DESC
-
Click File->Save As, Click Documents folder, and save the sql file with the name sample.sql.
-
Click Run on top left of query window.
-
Click View as Chart Icon on right of Results window.
-
Set Chart Type as horizontalBar and Data Direction to Vertical
-
Click Create Insight.
-
Right-click on the json snippet and click Format Document
-
Edit name as 'DB Space'
-
Select the whole JSON snippet and Copy all of it.
-
Click bottom-left gear icon, then Settings
-
Under User Settings on the right, find the last '}'. On the line above, add a comma to the end, press enter, then copy the snippet below:
"dashboard.server.widgets": [ { "name": "Tasks", "gridItemConfig": { "sizex": 1, "sizey": 1 }, "widget": { "tasks-widget": [ { "name": "backup", "when": "!mssql:iscloud" }, { "name": "restore", "when": "!mssql:iscloud" }, "configureDashboard", "newQuery" ] } }, { "name": "Search", "gridItemConfig": { "sizex": 1, "sizey": 2 }, "widget": { "explorer-widget": {} } }, { "name": "DB Space", "gridItemConfig": { "sizex": 2, "sizey": 1 }, "widget": { "insights-widget": { "type": { "horizontalBar": { "dataDirection": "vertical", "dataType": "number", "legendPosition": "none", "labelFirstColumn": false, "columnsAsLabels": false } }, "queryFile": "C:\\Users\\LabUser\\Documents\\sample.sql" } } } ]
-
Hit Ctrl+S to save your settings file
-
Right click localhost and click Manage. You should now be able to see the table spaces widget!
-
Open Visual Studio Code from the bottom task bar.
-
If the terminal is not already open, Hit Ctrl+` to open the Integrated Terminal Note: This is not the apostrophe, this is the grave accent below the ESC key.
-
Type
yo sqlops
and hit Enter. This opens the SQL Operations Studio Extension generator. This allows you to quickly get started on building an extension of your choice. -
To start off, use arrow keys and hit enter on New Dashboard Insight.
-
Follow these instructions:
- Add a full dashboard tab? Y
- What's the name of your extension? sample
- What's the identifier of the extension? hit enter
- What's the description of your extension? building a sample extension
- What's your publisher name? MSReady
- The publish name must be set, we recommend MSReady but you can use any publisher name.
-
You have now created a very simple extension. Now let's edit it.
-
Type
cd sample
into the terminal and hit enter. -
Type
code .
into the terminal and hit enter. This opens a new VS Code window, and shows the folder contents of what is currently in the Sample directory. -
Click sql and open query.sql to see our target insight extension.
-
Select and delete what is currently in query.sql.
-
Paste the following T-SQL:
------------------------------Data file size---------------------------- declare @dbsize table (Dbname nvarchar(128), file_Size_MB decimal(20,2)default (0), Space_Used_MB decimal(20,2)default (0), Free_Space_MB decimal(20,2) default (0)) insert into @dbsize (Dbname,file_Size_MB,Space_Used_MB,Free_Space_MB) exec sp_MSforeachdb 'use [?]; select DB_NAME() AS DbName, sum(size)/128.0 AS File_Size_MB, sum(CAST(FILEPROPERTY(name, ''SpaceUsed'') AS INT))/128.0 as Space_Used_MB, SUM( size)/128.0 - sum(CAST(FILEPROPERTY(name,''SpaceUsed'') AS INT))/128.0 AS Free_Space_MB from sys.database_files where type=0 group by type' -------------------log size-------------------------------------- declare @logsize table (Dbname nvarchar(128), Log_File_Size_MB decimal(20,2)default (0), log_Space_Used_MB decimal(20,2)default (0), log_Free_Space_MB decimal(20,2)default (0)) insert into @logsize (Dbname,Log_File_Size_MB,log_Space_Used_MB,log_Free_Space_MB) exec sp_MSforeachdb 'use [?]; select DB_NAME() AS DbName, sum(size)/128.0 AS Log_File_Size_MB, sum(CAST(FILEPROPERTY(name, ''SpaceUsed'') AS INT))/128.0 as log_Space_Used_MB, SUM( size)/128.0 - sum(CAST(FILEPROPERTY(name,''SpaceUsed'') AS INT))/128.0 AS log_Free_Space_MB from sys.database_files where type=1 group by type' --------------------------------database free size declare @dbfreesize table (name nvarchar(128), database_size varchar(50), Freespace varchar(50)default (0.00)) insert into @dbfreesize (name,database_size,Freespace) exec sp_MSforeachdb 'use [?];SELECT database_name = db_name() ,database_size = ltrim(str((convert(DECIMAL(15, 2), dbsize) + convert(DECIMAL(15, 2), logsize)) * 8192 / 1048576, 15, 2) + ''MB'') ,''unallocated space'' = ltrim(str(( CASE WHEN dbsize >= reservedpages THEN (convert(DECIMAL(15, 2), dbsize) - convert(DECIMAL(15, 2), reservedpages)) * 8192 / 1048576 ELSE 0 END ), 15, 2) + '' MB'') FROM ( SELECT dbsize = sum(convert(BIGINT, CASE WHEN type = 0 THEN size ELSE 0 END)) ,logsize = sum(convert(BIGINT, CASE WHEN type <> 0 THEN size ELSE 0 END)) FROM sys.database_files ) AS files ,( SELECT reservedpages = sum(a.total_pages) ,usedpages = sum(a.used_pages) ,pages = sum(CASE WHEN it.internal_type IN ( 202 ,204 ,211 ,212 ,213 ,214 ,215 ,216 ) THEN 0 WHEN a.type <> 1 THEN a.used_pages WHEN p.index_id < 2 THEN a.data_pages ELSE 0 END) FROM sys.partitions p INNER JOIN sys.allocation_units a ON p.partition_id = a.container_id LEFT JOIN sys.internal_tables it ON p.object_id = it.object_id ) AS partitions' ----------------------------------- select TOP 10 d.Dbname, --(file_size_mb + log_file_size_mb) as DBsize, --d.file_Size_MB, d.Space_Used_MB, --d.Free_Space_MB, --l.Log_File_Size_MB, l.log_Space_Used_MB--, --l.log_Free_Space_MB, --fs.Freespace as DB_Freespace from @dbsize d join @logsize l on d.Dbname=l.Dbname join @dbfreesize fs on d.Dbname=fs.name order by d.Space_Used_MB DESC
-
Open package.json. Under contributes and **dashboard.insights, change bar to horizontalbar and datadirection from horizontal to vertical.
If you are completely lost at this point, replace package.json contents with:
{
"name": "sample",
"displayName": "sample",
"description": "building a sample extension",
"version": "0.0.1",
"publisher": "msignite",
"engines": {
"vscode": "^1.27.0",
"sqlops": "*"
},
"categories": [
"Other"
],
"contributes": {
"dashboard.insights": [
{
"id": "sample.insight",
"contrib": {
"queryFile": "./sql/query.sql",
"type": {
"horizontalBar": {
"dataDirection": "vertical",
"dataType": "number",
"legendPosition": "none",
"labelFirstColumn": false,
"columnsAsLabels": true
}
}
}
}
]
,
"dashboard.tabs": [
{
"id": "sample.tab",
"title": "sample",
"description": "",
"container": {
"widgets-container": [
{
"name": "sample",
"gridItemConfig": {
"sizex": 2,
"sizey": 1
},
"widget": {
"sample.insight": {}
}
}
]
}
}
]
}
}
-
Open README.md and delete the contents inside the readme. Paste the following:
Sample insight widget extension.
-
Click File->Save All.
-
Hit CTRL+` to open the integrated terminal. Type 'vsce package' to package your extension. Type 'Y' and enter when prompted if you would like to continue without the repository field.
-
Use “Ctrl + C” to copy the file location of the vsix package from the terminal.
-
Open Azure Data Studio. Click File, then click Install Extension from VSIX package.
-
Paste directory link of extension and click Install. If you can't find it, try pasting: C:\Users\LabUser\sample\sample-0.0.1
-
Click Yes to third-party extensions on bottom-right, and Reload Now on bottom right.
-
Click on localhost to connect. Then right-click on localhost and click Manage
-
On the line next to Home, click Sample to see your sample extension.
-
Let's try adding multiple insight widgets. Go back to Visual Studio Code and add a new file under sql folder called query2.sql
-
Paste the following query.
Top Active Connections
SELECT count(session_id) as [Active Sessions] FROM sys.dm_exec_sessions WHERE status = 'running'
-
Now, go to package.json file so that we can create a new container for our widget. Find dashboard.insights.
-
Type or paste the following below the existing insight json content:
{ "id": "sample2.insight", "contrib": { "queryFile":"./sql/query2.sql", "type": { "count": { "dataDirection": "vertical", "dataType": "number", "legendPosition": "none", "labelFirstColumn": false } } } }
-
Find widgets-container. Type or paste the following:
{ "name": "sample2", "gridItemConfig": { "sizex": 2, "sizey": 1 }, "widget": { "sample2.insight": {} } }
-
Repeat Steps 13-19 and remember to Save All.
-
Using what you have learned, create two additional insight widgets using the following queries.
DB Buffer Usage (Use horizontalBar and vertical datadirection)
-- source:https://www.mssqltips.com/sqlservertip/2393/determine-sql-server-memory-use-by-database-and-object/ -- Use for a demo/sample purpose only. This query is not built-in to any product. DECLARE @total_buffer INT; SELECT @total_buffer = cntr_value FROM sys.dm_os_performance_counters WHERE RTRIM([object_name]) LIKE '%Buffer Manager' AND counter_name = 'Database Pages'; ;WITH src AS ( SELECT database_id, db_buffer_pages = COUNT_BIG(*) FROM sys.dm_os_buffer_descriptors --WHERE database_id BETWEEN 5 AND 32766 GROUP BY database_id ) SELECT TOP 10 [db_name] = CASE [database_id] WHEN 32767 THEN 'Resource DB' ELSE DB_NAME([database_id]) END, --db_buffer_pages, --db_buffer_MB = db_buffer_pages / 128, db_buffer_percent = CONVERT(DECIMAL(6,3), db_buffer_pages * 100.0 / @total_buffer) FROM src --ORDER BY db_buffer_MB DESC; order by db_buffer_percent DESC;
Thank you for attending this Microsoft Ready session. Now that you have learned to build your own Azure Data Studio extensions, we encourage you to continue to build extensions and contribute to our Extensions Marketplace.
To learn to build your own extensions:
- Get the prerequisites
- Follow along on our Github Wiki Get Started
- Read these blog posts:
Want to learn more about Azure Data Studio?
- Leave a star on our Github
- Download Azure Data Studio
- Report Issues or suggest Feature Requests on our Github Issues page
- Follow us on Twitter @azuredatastudio
Documentation
- Get Started
- Install Azure Data Studio
- Telemetry
- Microsoft Ready 2019 Lab
- MS Docs Overview
- Debug Trace Logging
- Troubleshoot Azure Authentication Issues
- FAQ
Contributing
- How to Contribute
- Developer Getting Started
- Submitting Bugs and Suggestions
- Localization
- Troubleshooting Build Issues
- Engineering FAQ
- How to update typings files
- Importing and using modules
- UI Guidelines
- Angular UI Guidelines
- Contributor License Agreement
- Azure Data Studio Tests
- Why is the Azure Data Studio license different than the repository license?
Tool Services
Extensibility Reference
- Getting Started
- Extensibility API
- Contribution Points
- Context Variables
- Servers and Data Explorer Tree Views
- Debugging with VS Code
- Extension Authoring
- Building multiple insight widgets
- Microsoft Ignite lab
- List of Extensions
- Replace sqlops namespace
Project Management