A Fine Slice Of SQL Server
Steve Jones asks, what’s in a name?:
I had someone ask me how to rename a SQL Server database recently. They were doing some development work and wanted to rename databases to test an application. I thought I remembered, but in this post, I show I learned something.
Read on for the answer, as well as some notes about it. One additional thing I’d point out is that renaming the database doesn’t rename the underlying files.
Comments closedSteven Sanderson asks, what’s in a name?
Think of
names()as your data janitor, cleaning up and assigning names to the elements in your objects. It’s a chameleon, working with vectors, lists, data frames, and more!
Read on to see how you can define (or change) names in various objects.
Comments closedSteven Sanderson renames factor levels of a categorical variable:
Before we jump into renaming factor levels, let’s quickly recap what factors are and why they’re useful. Factors are used to represent categorical data in R. They store both the values of the categorical variables and their corresponding levels. Each level represents a unique category within the variable.
Click through for three methods you can use to pull this off.
Comments closedAndy Leonard asks, what’s in a name?
I admit, this functionality may not be as useful for you as it is to me. Why do I like it so much? Well, I tweeted about it:
Read on for Andy’s reasoning, as well as one way that you can change a Microsoft Fabric workspace name.
If only we could change the name of Microsoft Fabric itself…
Comments closedIn this article I’m going to talk about the recent change that Microsoft has made in renaming the underlying database used in Power BI from the term “dataset” to “semantic model” (or as I would call it, “semantic data model”).
Read on to learn more about what the term means and why it makes sense in this context.
Comments closedChris Webb shares some thoughts:
The name change proved to be surprisingly uncontroversial. Of course it’s very disruptive – trust me, I know, I have around 500 blog posts that I need to do a search-and-replace on at some point – so I have a lot of sympathy for people with books or training courses that need updating or who are getting calls from confused end users who are wondering where their datasets have gone. But there was a general consensus that the change was the right thing to do:
Read on for a bit more of the story, as well as some great links to get additional information on semantic modeling.
Comments closedJohnny Winter shares some advice:
With Fabric being a unified platform, the worlds of Power BI Developer and Data Engineer collide. So is a solid naming convention a good idea?
At Advancing Analytics, we say yes.
In fact, given the breadth of the platform and the variety of artifacts available for use in Fabric, it becomes even more important to have a strategy to be able to organise these items and make them quick and easy to identify.
Read on to see what Johnny recommends.
Comments closedChad Callihan provides solid advice:
Everyone has an opinion on naming stored procedures. One opinion that can be agreed upon is that starting a stored procedure with “sp_” is not the way to go. Using “sp_” can only do harm. Let’s take a look at why that is.
Read on for Chad’s reasoning.
I don’t like prefixes at all for stored procedures (or tables). It’s a common misunderstanding of Hungarian notation, as you don’t provide any new and relevant information in the object name: of course it’s a stored procedure; I’m using “EXEC” to execute it, so what else could it be?
The exception to a very good rule is something which you intend to put in the master database and execute from any database context. The best example of this is sp_whoisactive.
Comments closedKendra Little disambiguates roles:
Much has changed: development patterns transformed from Waterfall to Agile, DevOps drives automation and shared ownership of code, and cloud services have made many more kinds of PAAS databases, data lakes, and data lakehouses available to organizations of all sizes.
These changes have introduced new and varied career paths for data folks which have different emphases on skill sets. In this post, I talk through the commonalities and differences between DBAs, Database Reliability Engineers (DBREs), and Data Engineers (DEs). Whether you’re a hiring manager or data professional, it’s worth knowing about these roles.
And a fourth one I’d include is Database Engineer, which I’ve also called a development DBA (versus a production DBA): focus on one platform, like SQL Server, and specialize in code development and tuning on that platform. I’d expect a Data Engineer to be familiar with at least one or two non-SQL programming languages—Python, Scala, Java, C#, F#, pick your poison—but that wouldn’t necessarily hold for a DBE.
Comments closedEitan Blumin gives everything a name:
This article was published by Aaron Bertrand a few years ago, talking about system-named constraints in SQL Server.
The article mostly focuses on the issue of naming conventions as the main issue with system-named constraints and provides a useful stored procedure script to generate sp_rename commands for all system-named constraints.
However, the script in the article provides the solution for only one database and doesn’t support the new “Edge Constraints” that were introduced in SQL Server 2019.
Check out Aaron’s article and Eitan’s follow-up piece.
Comments closed