{"id":104368,"date":"2024-10-31T01:08:50","date_gmt":"2024-10-31T01:08:50","guid":{"rendered":"https:\/\/www.red-gate.com\/simple-talk\/?p=104368"},"modified":"2024-10-31T01:08:51","modified_gmt":"2024-10-31T01:08:51","slug":"t-sql-notebooks-manage-views-source-control-and-more","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/blogs\/t-sql-notebooks-manage-views-source-control-and-more\/","title":{"rendered":"T-SQL Notebooks: Manage Views Source Control and more"},"content":{"rendered":"

T-SQL Notebooks is one of the new features announced during FabCon Europe.<\/p>\n

The most distracted could miss the fact this is a new feature at all. Yes, it is. Notebooks were capable to support Spark SQL, but T-SQL is something new.<\/p>\n

The main examples being announced are built with data warehouses, but let me confirm and highlight this:<\/p>\n

T-SQL Notebooks support lakehouses as well.<\/strong><\/p>\n

There is at least one limitation: DML is not supported with lakehouses.<\/strong><\/p>\n

\"A<\/p>\n

Let’s start from the beginning.<\/p>\n

The T-SQL Notebooks UI<\/h2>\n

The easiest way to create a T-SQL notebook is using the button “New Query” at the top of a lakehouse of Data Warehouse. The button has options, and the new one is “New SQL Query in Notebook”<\/p>\n

\"A<\/p>\n

Once the notebook is created, it’s like a regular notebook. You can change the notebook type at the top if you want, but T-SQL is already selected by default.<\/p>\n

\"A<\/p>\n

It has an explorer of warehouses attached, but they can be lakehouses as well. Exactly as in a regular notebook, you can set a default when there are many sources attached. The name of the option is different: “Primary Warehouse”.<\/p>\n

\"A<\/p>\n

Another interesting feature is the button “Create Table”, allowing to transform any SQL query created in the notebook in a new table<\/p>\n

\"A<\/p>\n

Scheduled Tasks for Warehouses<\/h2>\n

When using the T-SQL notebooks with warehouses, they can be used for the most expected purpose: You can create scheduled processes using the notebooks.<\/p>\n

In this way, a team who choose to work with a warehouse doesn’t need to use pySpark to schedule something, they can use pure T-SQL.<\/p>\n

Version Control for Lakehouse T-SQL Objects<\/h2>\n

I suffer with this problem right now, in a solution I work on. How to make version control of lakehouse objects, especially views?<\/p>\n

The creation of views is made using the queries created in the SQL Endpoint UI. There is no way to make a version control of these queries.<\/p>\n

\"A<\/p>\n

T-SQL notebooks support the creation of views. We can replace the queries in SQL Endpoints by T-SQL notebooks. We can add them to source control and in this way control the version of the views.<\/p>\n

\"A<\/p>\n

Of course, the notebooks also support deployment pipelines. We can easily use DevOps to create a release pipeline promoting the notebook from one stage to another, executing it in the new stage and making a commit in the workspace.<\/p>\n

Summary<\/h2>\n

This is a great advance in source control, and a very unexpected one: While thinking about making an advance on processing creation for a data warehouse, a great advance in source control for lakehouses was also achieved<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

T-SQL Notebooks is one of the new features announced during FabCon Europe. The most distracted could miss the fact this is a new feature at all. Yes, it is. Notebooks were capable to support Spark SQL, but T-SQL is something new. The main examples being announced are built with data warehouses, but let me confirm……<\/p>\n","protected":false},"author":50808,"featured_media":104376,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2,159164],"tags":[158998,158997,159035,101611,4183],"coauthors":[6810],"class_list":["post-104368","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blogs","category-microsoft-fabric","tag-lakehouse","tag-microsoft-fabric","tag-notebook","tag-power-bi","tag-t-sql"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/104368","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/users\/50808"}],"replies":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/comments?post=104368"}],"version-history":[{"count":1,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/104368\/revisions"}],"predecessor-version":[{"id":104377,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/104368\/revisions\/104377"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/media\/104376"}],"wp:attachment":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/media?parent=104368"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/categories?post=104368"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/tags?post=104368"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/coauthors?post=104368"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}