A Fine Slice Of SQL Server
Charles Thibault explains why you might not want to use logistic regression at all:
I wrote a post on my LinkedIn about why you should NEVER run a Logistic Regression. (Unless you really have to).
Click through for the kernel of the argument or check out the video.
Comments closedArun Sirpal shows how to connect your Databricks cluster to Power BI:
A very common approach is to query data straight from Databricks via Power BI. For this you need Databricks token and the JDBC address URL. This is found within Account settings of the cluster.
Read on to see how to get this token and how to connect to Databricks using it.
Comments closedChris Johnson troubleshoots an issue in code:
The poster had a
CASEstatement and was wondering why it didn’t work as expected. Essentially they were doing something like:
CASE WHEN @a = @b OR (@a IS NULL AND @b IS NULL) THEN 1 ELSE 0CASE WHEN NOT(@a = @b OR (@a IS NULL AND @b IS NULL)) THEN 1 ELSE 0And they wanted to know why both were returning 0 when
@aor@bwere set toNULL. The issue here is that any normal predicate involvingNULLreturns an unknown. They had tried to compensate with theOR, which got them the result they wanted in the first statement, but didn’t understand why it did that.
Click through for the explanation.
Comments closedSteve Hughes walks us through three Elastic concepts in Azure:
Elastic queries allow developers to interact with data from multiple databases supported on the Azure SQL database platform including Synapse. Elastic queries are often referred to as Polybase which is currently implemented in SQL Server 2019 and Azure Synapse. The key difference is that elastic queries only allow you to interact with other Azure SQL Databases but not Hadoop or other database implementations (e.g. Teradata or Oracle). Part of the confusion comes from the fact that the implementation looks very similar. Both toolsets use external tables in SQL Server to interact with the connected data sources. However, Polybase requires additional components to run whereas elastic queries are ready to go without additional setup.
Read on for more information, including demos.
Comments closedSoheil Bakhshi reminds me of DB/2:
So, here is my scenario. I received about 10 files, including 15 tables. Some tables are quite small, so I didn’t bother. But some of them are really wide like having between 150 to 208 columns. Nice!
Looking at the column names, they cannot be more difficult to read than they are, and I have multiple tables like that. So I have to rename those columns to something more readable, more on this side of the story later.
Fortunately, there’s a way to fix this; click through for that way.
Comments closedAdrian Hills takes us through using Azure Table Storage:
Azure Table Storage is a NoSQL key-value PaaS data store that can be a great option for highly scalable, highly available systems. It supports storing petabytes of data and a flexible data schema, meaning different entities in the same table can have different schemas. References to NoSQL databases having “flexible schema” or being “schema-less” can give the impression that database schema design is a thing of the past and that you can bypass it and focus more on the application code. The reality is, even in this NoSQL world, schema design is very important and if you don’t give it due care and attention, then it can come back to bite you.
If you have a RDBMS background and are new to Azure Table Storage, it’s common to find yourself “thinking in SQL” and trying to solve database modeling requirements with a SQL approach before then trying to translate that to a key-value mindset. In this blog post, I’ll cover some of the fundamentals of Azure Table Storage and dive into some common questions you might find yourself asking about Azure Table Storage. Where code samples or references are applicable in this blog post, we’ll be focusing on .NET and using the Azure SDK (specifically relating to the Microsoft.Azure.Cosmos.Table nuget package).
Read on for the full story.
Comments closedDavid Klee continues a video series:
If you followed the last video, I showed you how to set up windows perfmon for ongoing performance metric collection on all of your critical SQL Server machines. However, having this raw data in a portable format doesn’t mean you have an easy means to access that data. In this training video, I show you a PowerShell script that we released that helps you export this data into a SQL Server database table so that you have access to the raw data to perform ongoing performance analysis with whatever favorite tool you prefer.
David walks through the process in a video, so check it out.
Comments closedAndy Levy takes us through the Get-History cmdlet:
I’m sure that a lot of folks do work on the PowerShell command line, trying various things, before committing to writing a full script or function. Work it out step by step, try a few different things, etc. But once you’ve finished, how can you turn it into a script? Let’s take a look.
Read on for that look.
Comments closed