A Fine Slice Of SQL Server
Richard Swinbank re-uses a pipeline:
Implementation of one pipeline per report makes additional demands of a developer when creating a new report. To make this easier to manage, in this post I look how to make pipeline creation as simple as possible, by building each pipeline from a set of reusable components.
Click through to see how this works in Azure DevOps. I’d expect the process to be reasonably similar for GitHub Actions as well.
Comments closedVytas Suopys covers a bit of source control strategy:
Have you ever deployed a release to production only to find out a bug has escaped your testing process and now users are being severely impacted? In this post, I’ll discuss how to deploy a fix from your development Synapse Workspace into a production Synapse Workspace without adversely affecting ongoing development projects.
This example uses Azure DevOps for CICD along with a Synapse extension for Azure DevOps: Synapse Workspace Deployment. In this example, I assume Synapse is already configured for source control with Azure DevOps Git and Build and Release pipelines are already defined in Azure DevOps. Instructions on how to apply this this can be found in the Azure Synapse documentation for continuous integration and delivery.
The specific example covers Synapse, though the general principle applies no matter what you’re deploying.
Comments closedRichard Swinbank deploys a report:
In the first post in this series, I built an Azure DevOps pipeline to automate steps in a Power BI development workflow. The pipeline implemented a very basic workflow – as soon as a developer committed a new report version to Git, the pipeline deployed it immediately into a Power BI workspace.
In this post I’ll be building a pipeline to support a more sophisticated workflow that enables peer review and stakeholder testing.
Click through for the step-by-step process.
Comments closedKevin Chant takes us to the edge:
Azure SQL Edge is a version of the SQL database engine that is designed to be deployed on IoT (Internet of Things) devices.
It is based on SQL Server 2019. Which means that by default all new databases are created using the SQL Server 2019 compatibility level. You can lower the compatibility level all the way down to SQL Server 2008 if required.
There was some nice functionality in Azure SQL Edge, some of which (like DATE_BUCKET() and DATETRUNC() made it into SQL Server 2022).
Kevin Chant uses a deployment tool to install a deployment tool for his deployment tools:
I decided to do this post after some feedback I received about SqlPackage after a series of posts about deploying dacpacs to serverless SQL Pools. For example, my post about deploying a dacpac to a serverless SQL pool.
Because in order to deploy dacpacs to serverless SQL Pools you must update SqlPackage.
With this in mind, I thought I better go through various ways to update SqlPackage if intending to use it to deploy dacpacs to serverless SQL Pools.
Read on to see how you can do this.
Comments closedOlivier Van Steenlandt publishes to Azure SQL Database:
During the step-by-step example, we will download the Pipeline Artifact created in my previous blog post. Afterwards, we configure the steps to deploy to Azure SQL. Near the end of this blog post, I will also include a link to my version of the YAML file.
Click through for those instructions.
Comments closedOlivier Van Steenlandt busts out the YAML:
In previous blog posts, I explained how to automate the Database Project Build & Deployment process using Azure DevOps (Release) Pipelines. These blog posts focused on setting up as easily as possible using the Classic Editor.
In this blog post, I’m going through the steps of setting up a build pipeline using YAML.
Read on to learn why the YAML-based approach is the best option for ADO and how to build a pipeline.
Comments closedTing Chou builds a proof of concept:
Few days ago, I asked myself a question about how can you better manage all the database changes defined in SQL scripts with DDL (Data Definition Language)? Maybe try to use version control on the SQL code and then use DevOps pipelines to achieve continuous deployment. Then, I came up with a poc solution, choux130/DevOps_In_DE/jenkins_mysql_flyway.
Click through for the repo, as well as a few TODOs.
Comments closedAlexander Billington shares a few tools and tips:
Machine learning (ML) model deployment is a critical part of the MLOps lifecycle, and it can be a challenging process. In the previous blog, we explored how Azure Functions can simplify the deployment process. However, there are many other factors to consider when deploying ML models to production environments. In this blog, we’ll delve deeper into some of the essential hints and tips for more robust model deployments. We’ll look at topics such as proper model versioning and packaging, data validation, and performative code optimisations. By implementing these practices, data scientists and ML engineers can ensure their models are deployed efficiently, accurately, and with minimal downtime.
MLflow is definitely a good recommendation, as is Pydantic (which is on my to-learn list…one of these days).
Comments closedStephanie Bruno does a bit of continuous integration:
There’s a lot of information on how to get around the lack of an out-of-the box CI/CD solution for Power BI datasets, but for me it’s often complicated and I have to read too many pages before making much progress on my own. This post is here to strip it down and provide you with the easiest way we know to enable a bonafide CI/CD process for Power BI datasets with Azure DevOps. The post is still longer than we’d like, but it includes detailed step-by-step instructions to walk you through every part of the process. To save space, we used slideshows for the screenshots, but you can pause them as you follow along.
There are a lot of steps but the goal is a worthwhile one.
Comments closed