Azure Stretch Database, Part I: Getting Going
With most innovative new technologies, Azure Stretch Database demos make it look completely easy. Here is a step by step to get going, with examples. Part One of a Two-Part series.
2019-08-26
4,957 reads
John F. Tamburo
Making Good Use of SQL Server Auditing
SQL Server Auditing is a powerful out-of-the box toolset that captures auditing information and writes to a file or the Event Log. This article examines the little things that might snag you up.
2019-08-05 (first published: 2017-10-05)
11,206 reads
DBAs and the ITIL Framework, Part II: Asset Management
See how the ITIL Framework's Asset Management standards make the DBA's job easier. Use the CMDB and DML to keep your data assets under tight control.
2019-05-17 (first published: 2017-11-21)
3,616 reads
Database Cloning Tools in Lower Environments
With exciting products like SQL Clone making their debut, the DBA will need to think through the approach to implementing such powerful tools. Done properly, these tools will provide a massive benefit to both the DBA and developer.
2019-05-10 (first published: 2017-11-28)
4,394 reads
Understanding Peer-to-Peer Transactional Replication, Part 3
We've gone through the basics of Peer-to-Peer Transactional Replication (PPTR). Now, we will blow it up! We will then fix it and show you how you how to triage and repair PPTR. When you remain calm and take some easy steps, you can stabilize PPTR with ease.
2019-01-04 (first published: 2016-01-07)
2,984 reads
Understanding Peer-to-Peer Transactional Replication, Part 2
As the Peer-to-Peer series continues, we set up an example topology in Peer-to-Peer Transactional replication and test it.
2018-12-28 (first published: 2015-11-05)
4,128 reads
Understanding Peer-to-Peer Transactional Replication, Part 1
There are times when you need to share tables between servers, where the table may be updated in both places. Peer-to-Peer Transactional Replication gives you the ability to create a solution. I explain the benefits and the downfalls.
2018-12-21 (first published: 2014-01-13)
6,262 reads
SQL Authentication Via AD Groups Part II: Who has what access?
In a previous article, we discussed how to liberate the DBA from SQL Logins with AD Groups. A good point was raised: How can the DBA know who has what access? Here is a solution.
2018-08-03 (first published: 2016-02-18)
12,254 reads
Packaged-Application Database Nightmares - A Horror Story
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?
2018-05-02 (first published: 2015-12-22)
5,448 reads
Random Word Generation for Data Scrubbing
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.
2018-05-01
5,889 reads
Blogs
Advice I Like: Art
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
Why Optimize CPU for RDS SQL Server is a game changer
One feature that I have been waiting for years! The new announcement around optimize...
Performance tuning KubeVirt for SQL Server
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
Forums
i noticed the sqlhealth extende event is on by default , so can i reduce
hi, i noticed the sqlhealth extended event is on by default , and it...
New-AzSqlInstanceServerTrustCertificate - Failed and no clues
Using New-AzSqlInstanceServerTrustCertificate to import a certificate and get the message New-AzSqlInstanceServerTrustCertificate: Long running operation...
Refactoring SQL Code
Comments posted to this topic are about the item Refactoring SQL Code, which is...
Question of the Day
The Read Committed Snapshot Isolation behaviour
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers