A Fine Slice Of SQL Server
Tomaz Kastrun starts the stopwatch:
When you are working with large datasets performance comes to everyone’s mind. Especially when converting datasets from one data type to another. And choosing the right method can make a huge difference.
So in this case, I will be creating a dummy list, and I will convert the values in the list into data.frame.
Click through for a variety of techniques and how well they performed. There are some good solutions in the comments as well.
Comments closedRobert Cain continues a series on KQL:
There are versions of these which are case sensitive. We’ll see a few here, focusing on the
containskeyword. In addition there are not versions, which will also be demonstrated.There is another operator we’ll discuss here,
in. It is a bit of an odd duck, in that it is case sensitive by default. We’ll see it and its variants later in this post.
Case sensitivity in search is a curse.
Comments closedGrant Fritchey provides an overview:
In this article I’m going to go over the different types of indexes and some index behaviors. We’ll get into what the indexes are, how they work, and how best you can apply them within your databases. I’m hoping you’ll develop an understanding of which indexes are likely to work better in each situation.
However, I won’t be covering the indexes in detail. Further, I won’t be going very far into how these indexes affects performance. I’m not yet up on performance tuning within PostgreSQL. That article is quite a way down the track from here. When you know which index to use where, you can then drill down to better understand that index, and how best to measure the performance impacts.
This set of indexes is quite different from what we’re used to in SQL Server and much closer to what you get in Oracle.
Comments closedNicky van Vroenhoven goes the extra mile:
Last night we had a work meeting at Powerdobs, with a few presentations about business updates, new joiners in the coming months and Power BI projects. I had the pleasure of closing the evening with a presentation on Power BI.
So I decided to do a presentation on my favourite additions to Power BI over the past year. But instead of doing a regular PowerPoint presentation, I decided to do an all-Power-BI presentation. It was very well received and I was encouraged to share it here!
Click through for the embedded report. Great job by Nicky to put this together.
Comments closedWarwick Rudd continues a series on Azure Arc-Enabled Data Services. Part 9 covers database restoration:
Now that we have our Azure Arc-enabled SQL Managed Instance deployed, potentially one of the most common tasks you will need to undertake is being able to perform a database restore of an existing database to your newly provisioned Azure Arc-enabled SQL Managed Instance.
In our previous post, we deployed our Azure Arc-enabled SQL Managed Instance – “ae-sqlmi-demo” that we will continue to investigate and learn about how we can utilize in our data environments. In this post, we are having a look at restoring a database.
Part 10 looks at upgrade management:
Comments closedManaging your Data Controller through Azure Data Studio provides an easy approach for controlling when you wish to apply upgrades supplied by Microsoft. This is something you need to stay on top of as the upgrade path is an incremental approach and only allows you to upgrade to the next version. If you leave it too long, you could be faced with multiple upgrades to be undertaken. This could lead to extended outages while you get up to date.
Olivier Van Steenlandt continues building out a database project:
A Pull Request is an alternative way of merging branches. Instead of executing the merge yourself, you will create a Pull Request for someone else to revise your development and approve and merge when ok. By doing this you are introducing peer reviewing into your development process. From my experience, using Pull Requests will improve your development quality since someone needs to validate your changes before they can be deployed to a certain environment.
I wouldn’t advise using Pull Requests to get changes in a development environment but I would advise using it to get changes to an Acceptance- or Production environment. By doing this, you can already find issues in an earlier stage than in production.
Read on to see how they work, using Azure DevOps as the example. GitHub pull requests are very similar in nature.
Comments closed