In SQL Server Master Data Services all the entities are organized in a model. Once a model is ready to be released to subscribers, it should be frozen and marked as ready for subscribers. Until a model is marked as ready, a model is typically deemed as work in progress. In this article, Siddarth Mehta covers the standard process that's required to release a completed version of the model to subscribers.
2016-06-17
2,721 reads
Knut Jürgensen shares his experiences, both positive and negative, with regard to the function that Master Data Management fulfils within a company. Too often this critical aspect of a business is overlooked or pushed aside without paying it the attention it deserves based on the cost benefits available.
2016-06-16
4,935 reads
In the third part of his series on Row Level Security (RLS), Greg Larson shows how to disable RLS for database administrators, sysadmins, and database owners.
2016-06-15
6,385 reads
Paul White discusses the internals of SQL Server's WITH ENCRYPTION clause, and explains why it is not as safe as you might think.
2016-06-14
3,877 reads
The worst part for a DBA of getting started with PowerShell is often just figuring out the best way of working with SQL Server. The most suitable approach to accessing SQL Server depends on the sort of task you need to produce a script for. Laerte Junior aims at a simple guide to the most common approaches and when to use them.
2016-06-14
3,826 reads
IronPython is a Python implementation build on .NET. This article shows how you can use IronPython to access SQL Server Management Objects.
2016-06-13
3,780 reads
Automated configuration management is simpler with Desired State Configuration (DSC) and Push mode, but what is the best way to use DSC to automate deployments on your machines? ‘Push’ mode or ‘Pull’ mode? How can you reduce configuration-drift over time? Nicolas Prigent describes the second DSC deployment mode: Pull mode.
2016-06-13
3,500 reads
Using the APPLY operator to reduce repetition and make queries DRYer.
2016-06-10 (first published: 2015-04-02)
22,796 reads
There are several decisions to be made when designing indexes for Memory-optimized tables in In-Memory OLTP, and to make the best choice, it pays to understand something about the nature and usage of memory-optimised indexes. Murilo Miranda continues his series by explaining how such an index is unlike a conventional index.
2016-06-10
4,346 reads
Inside SQL is the Deep Dive conference for SQL Server professionals in London on June 14.
2016-06-09
3,538 reads
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...
We need to replace our Windows server running SQL 2017. Any reason not to...
Comments posted to this topic are about the item Using OPENJSON
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