Reasons to Upgrade
There are always reasons to upgrade or avoid upgrading to a new version. Steve Jones has a few thoughts.
There are always reasons to upgrade or avoid upgrading to a new version. Steve Jones has a few thoughts.
In the third installment of this series, Steve Jones uses PowerShell to source control code.
Some time ago, Phil Factor wrote his booklet 'SQL Code Smells', collecting together a whole range of SQL Coding practices that could be considered to indicate the need for a review of the code. It was published as 119 code smells, even though there were 120 of them at the time. Phil Factor has continued to collect them and the current state of the art is reflected in this article. SQL Prompt is committed to cover as many as possible of them. Phil has also updated his book, which is free to download.
The business decides on a packaged application and buys it. After installation, you look at the schema and realize that is is a nightmare. How do you manage this nightmare?
There's a sale on the price of SQL Server for Linux and Steve wonders if people will move.
In this post, Tim Smith will look at some of the considerations for both data rules and logic to prevent invalid data early in the ETRL process.
Steve likes that idea of auto deleting data, especially with legislation increasing.
With HIPAA and GDPR requiring your careful scrubbing of data for lower environments, random word generation promises to be a huge helper. Read here how to do it.
Microsoft currently offers two built-in methods of running production SQL Server databases in Azure. The first relies on the ability of Infrastructure-as-a-Service (IaaS) Azure virtual machines to host a variety of on-premises workloads, including SQL Server instances. The second one leverages Platform-as-a-Service (PaaS)-based Azure SQL Database. With the introduction of the Azure SQL Managed Instance service, you have a third option, which combines the benefits of its two predecessors.
Every organization I talk to has the same problem dressed up in different clothes....
By DataOnWheels
I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
Comments posted to this topic are about the item The day-to-day pressures of a...
Comments posted to this topic are about the item Data Modeling with dbt for...
Comments posted to this topic are about the item Data Modeling with dbt for...
I have some data in a table that looks like this:
BeerID BeerName brewer beerdescription 1 Becks Interbrew Beck's is a German-style pilsner beer 2 Fat Tire New Belgium Toasty malt, gentle sweetness, flash of fresh hop bitterness. 3 Mac n Jacks Mac & Jack's Brewery This beer erupts with a floral, hoppy taste 4 Alaskan Amber Alaskan Brewing Alaskan Brewing Amber Ale is an "alt" style beer 8 Kirin Kirin Brewing Kirin Ichiban is a Lager-type beerIf I run this, what is returned?
select t1.key
from openjson((select t.* FROM Beer AS t for json path)) t1 See possible answers