Additional Articles


External Article

Master Data Services – The Basics

Master Data Services (MDS) is Microsoft's platform for supporting Master Data Management (MDM). A system like MDS, if properly maintained, gives organisations a powerful alternative to increasingly having to centralize databases as a way of preventing data from getting out sync or become inconsistent, and a reliable way of managing the flow of data through corporate IT systems. It makes microservice architectures realistic. Hari Yadav shows you how to get up and running with MDS.

2016-10-25

4,165 reads

External Article

PowerShell Just Enough Administration

A major difficulty for a System Administrator who wishes to provide access for auditors, Helpdesk staff, developers and other IT people is that adminstrator roles give users more access than they need. It is too easy to make mistakes, or to make more changes than those that were signed-off. With JEA, it is possible to create role-based access control (RBAC) endpoints that define precisely what actions you’ll let your users carry out without needing a elevated, privileged administrator credentials, and which log and report all operations.

2016-10-19

3,276 reads

External Article

In-Memory OLTP: Row Visibility in SQL Server’s MVCC

SQL Server's In-memory OLTP is fast, due to its multi-valued concurrency control (MVCC). MVCC avoids the need for locks by arranging for each user connected to the database to see a snapshot of the rows of the tables at a point in time, No changes made by the user will be seen by other users of the database until the changes have been completed and committed. It is conceptually simple but does the user always see the correct version of a row under all circumstances? Shel Burkow explains.

2016-10-17

3,150 reads

External Article

DELETE Operation in SQL Server HEAPs

You should stick to using tables in SQL Server, rather than heaps that have no clustered index, unless you have well-considered reasons to choose heaps. However, there are uses for heaps in special circumstances, and it is useful to know what these uses are, and when you should avoid heaps. Uwe Ricken explains, and demonstrates why you'd be unwise to use heaps rather than tables when the data is liable to change.

2016-10-14

3,646 reads

Blogs

The First Steps: Understanding the Basics of FinOps

By

As a DevOps professional, I’ve seen firsthand how cloud costs can quickly spiral out...

Monday Monitor Tips: AI Query Analysis

By

AI is everywhere. It’s in the news, it’s being added to every product, management...

AI: Blog a Day – Day 8: RAG – Retrieval Augmented Generation

By

RAG — Retrieval Augmented Generation. we have covered so far — embeddings, vectors, vector...

Read the latest Blogs

Forums

would it be so terrible to install ssms on a few user desktops?

By stan

Hi, ssms is free here.   I can think of other reasons to do this...

I'm thinking about submitting some articles

By Doctor Who 2

I've written some documentation on using different Markdown types of files on GitHub. It's...

Not Just an Upgrade

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Not Just an Upgrade

Visit the forum

Question of the Day

Restoring On Top I

I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?

USE Master
BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO

USE DNRTest
GO
CREATE TABLE MyTest(myid INT)
GO
USE master
RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACE

See possible answers