A Fine Slice Of SQL Server
Hugo Kornelis looks at the execution plan:
Welcome to part twenty-one of the plansplaining series, where we will continue our look at execution plans for graph queries. In the previous post, we looked at the internal structure of node and edge tables, and discovered that they have a few hidden columns. Now let’s look how those columns are used in graph queries.
Read on for the example and a deeper dive into how graph tables actually work.
Comments closedSantosh Hari looks at the options:
Azure docs have a great page on the various load balancing options in Azure that even has an awesome flowchart summing up the choices. However, not being from a networking background, combined with Microsoft’s “special” naming, combined with some sort of memory issue recalling these names from memory meant that even if I had to rely on rote memory when in conversations with customers, I would often mix up the names. For instance, confuse traffic manager and load balancer. So, I decided to understand some of the basics behind cloud load balancers to help become a more interesting conversationalist in this topic: “well actually, you should be using an app gateway there, John”.
This often isn’t in the database administrator’s purview, but Santosh does a good job of explaining the concepts and, if you’re hosted in Azure, it is good to know what’s sitting in front of your database.
Comments closedLeila Etaati shows off some new functionality:
One of the interesting features of the New Card visual is the capability to add images to the Card visual.
It added more context to the car visual.
In this blog post, I will show some data related to cancer in New Zealand based on gender and cancer type.
Read on for the example.
Comments closedThom Andrews solves a problem:
Notice that the error line states line 2 not line 8, which is the line the
sys.sp_executesqlwas called on. Knowing the line the error occured on within the dynamic batch is certainly important, but if you’re working with multiple dynamic batches you have no way of knowing which dynamic batch might have produced the error; was it the one executed on line 100? Line 200? Line 350?Solving this problem wasn’t wasn’t exactly simple, and it came with a couple of caveats.
Click through for the approach. As Thom mentions, it isn’t perfect, but it is reasonable and interesting.
Comments closedDustin Vannnoy has two of the three R’s down:
Every Spark pipeline involves reading data from a data source or table. For data engineers we usually end the pipelines by writing the transformed data. In this tutorial we walk through some of the most common format and cloud storage locations for reading and writing with Spark. We’ll save some of the advanced Delta Lake capabilities for another tutorial.
Click through to see how to read from and write to CSV, JSON, and Parquet formats. Dustin has examples of working with Azure Blob Storage, S3, and Google Cloud Storage, and even some database examples with JDBC.
Comments closedSteven Sanderson shows off the ability to perform crosstabs in R:
As a programmer, you’re constantly faced with the task of organizing and analyzing data. One powerful tool in your R arsenal is the xtabs() function. In this blog post, we’ll explore the versatility and simplicity of xtabs() for aggregating data. We’ll use the
mtcarsdataset and thehealthyR.data::healthyR_datadataset to illustrate its functionality. Get ready to dive into the world of data aggregation with xtabs()!
Click through for two examples of it creating a crosstab (or, in SSRS/Power BI terms, a matrix) from your data.
Comments closedRichard Swinbank has an image for us:
I spent some time working at a property portal, where users could look at online listings of homes for sale or rent, then go on to book a viewing appointment with an estate agent. On one occasion we were asked to build a Power BI report showing:
- the number of appointments booked by portal users
- the percentage of appointments where the user had viewed the online listing more than once.
Sounds easy enough, right?
Click through for the image. It makes intuitive sense, but is a good visual depiction of why some data requests are more challenging than others.
Comments closedPatrick Gruenauer checks download speed:
Short explanation: A file will be downloaded from my homepage. It’s a video about Powershell Profiles in German language. During the download of the file the process is measured with the Measure-Command cmdlet. At the end we get the final result and the time it took to download the file.
You can, of course, change the file location to whatever makes sense, but it’s nice to have something handy and not need to go to any websites for a speed test.
Comments closedMatthew McGiffen has a primer for us:
Statistics are vitally important in allowing SQL Server to find the most efficient way to execute your queries. In this post we learn more about them, what they are and how they are used.
Read on for plenty of information about stats. One thing I’d emphasize in this is that, for the most part, auto-generated stats are fine. The only time I’ve ever seen any value in creating my own stats is in multi-column statistics (which auto-generated stats doesn’t do), and even that’s of fairly limited value, at least in my experience. I’m sure that there’s a point in which hand-crafting your own statistics makes a tiny but noticeable marginal difference, but the systems I’ve worked with tend not to be anywhere near that point. There are usually much bigger fish to fry.
Comments closedJose Manuel Jurado Diaz has a script for us:
Today, we encountered an interesting service request of attempting to reduce the load times for 100,000 records from a table with 97 varchar(320) fields in an Azure SQL HyperScale database. Following, I would like to share my lessons learned here.
The idea is to split in different concurrent process the execution of multiples SqlBulkCopy. In this case, we are going to split this process in 5 processes running in parallel inserting 20,000 rows, let’s try to know the total size.
Read on for the script, as well as a rough idea of how long it’ll take inserting into an Azure SQL DB Hyperscale instance.
Comments closed