A Fine Slice Of SQL Server
Richard Swinbank fights Visual Studio:
I sometimes find working with Visual Studio’s projects a challenge in multi-developer environments, because each project type seems to have its own vulnerability to Git merge conflicts. In the case of SSAS tabular, I’ve found two issues to be a regular source of conflicts:
Click through to see what those two causes are and what you can do to reduce the risk of having either one burn you.
Comments closedMeagan Longoria finds an oddity with Azure Data Factory:
When I arrived at the Git configuration page, I found the Disconnect button to be disabled. This was confusing as I am an Owner and Data Factory Contributor on this resource.
Read on to see how Meagan was able to fix this issue, and also the underlying cause of the problem.
Comments closedKa-Hing Chueng and Vaibhav Sethi announce Databricks Repos is now generally available:
Thousands of Databricks customers have adopted Databricks Repos since its public preview and have standardized on it for their development and production workflows. Today, we are happy to announce that Databricks Repos is now generally available.
Databricks Repos was created to solve a persistent problem for data teams: most tools used by data engineering/machine learning practitioners offer poor or no integration with Git version control systems, forcing them to navigate through multiple files, steps and UIs to simply review and commit code. Not only is this time-consuming, but it’s also error-prone.
This has been a bit of a pain point with Databricks in the past, and they’ve come up with this solution. Given that Azure Synapse Analytics has some of the same pain points, I’d expect we’ll see something similar in time.
Comments closedAdam Saxton hits on an important topic:
Can we use source control with Power BI? We get this question ALL THE TIME! Adam walks you through what your options are and how this works today with Power BI.
Read on to learn Adam’s answer.
Comments closedDeborah Melkin shows off a feature of Azure Data Studio:
If you read my T-SQL Tuesday post from this month, I mentioned that I’ve been using Azure Data Studio on daily basis. One of the things that I find I use it for the most is for Source Control with Git. I’m incredibly surprised by this. Maybe it comes from years of using Management Studio and not being able to check in code from the tool that I’m using to write it. (Or maybe I’ve been able to do that all this time and no one told me…?)
As I’m using it, I found two things that have helped me out. So naturally, I thought I’d share.
Click through for information on how to use multiple repos, as well as a bonus item.
Comments closedElizabeth Noble has a new video for us:
In many companies, you’re often working with more than one database on the same server. When I use Visual Studio, I have all the databases that exist on the same server in the same solution. You can do this same thing when you’re working with Azure Data Studio.
Click through to see how.
Comments closedAhmad Yaseen shows how you can save Azure Data Factory pipelines in source control:
To overcome these limitations, Azure Data Factory provides us with the ability to integrate with a GIT repository, such as Azure DevOps or GitHub repository, that helps in tracking and versioning the pipelines changes, and incrementally save the pipeline changes during the development stage, without the need to validate the incomplete pipeline, preventing these changes from being lost in case of any crash or failure. In this case, you will be able to test the pipeline, revert any change that is detected as a bug, and publish the pipeline to the Data Factory when everything is developed and validated successfully.
Click through for the setup instructions.
Comments closedElizabeth Noble shows how you can get your brand new Azure Data Studio project into GitHub:
Once you have the database project created, you’ll want to get your database project added to source control so that you (and others) can modify and manage your database code. This next step is the beginning of allowing you and others to work on the same databases and minimize the risk of overwriting someone else’s work or deploying the wrong code to Production.
Tools like GitHub Desktop and SourceTree have definitely made things easier, especially for the happy path scenarios.
Comments closedElizabeth Noble has a new video for us:
In this week’s YouTune video, I show how you can clone (import) a repository (database code) from GitHub all within Azure Data Studio. This is a great feature that helps make database source control more accessible to individuals who may not have access or be comfortable using Visual Studio or VS Code.
Click through for the video.
Comments closedKevin Chant shares some thoughts:
In this post I want to cover more thoughts about SQL Server professionals using version control. Because I have had some interesting conversations since my last post about it.
In a previous post I covered how SQL Server professionals can benefit from using version control. Which you can read in detail here.
Now I want to clarify a few things relating to it as well.
Read on for those thoughts.
Comments closed