Test Data

External Article

10 tips for Test Data Management success

  • Article

What are the challenges to implementing a successful test data management strategy? In our recent webinar ‘Harnessing the Power of Test Data Management: Strategies for Success’, Redgate’s Steve Jones was joined by Hamish Watson (DevOps Consultant) and Daniel Watkins (Director/Principal Consultant) to talk all things TDM and how to implement it efficiently and effectively. Here are 10 key tips and takeaways from their conversation in a short blog post.

2024-08-16

External Article

Redgate recommended in Bloor Test Data Management market update

  • Article

Last year, Redgate announced the launch of their latest in test data management (TDM) technology – Redgate Test Data Manager. This year, they’re proud to have been recommended in Bloor’s 2024 Test Data Management Market Update! This paper highlights the increasing adoption of TDM technology among enterprise organizations and offers insight into the trends and approaches to look out for when looking for a TDM solution.

2024-07-10

External Article

Concepts and Issues in Test Data Generation

  • Article

Data generation is the science and art of providing data for database development work that is as realistic and controllable as possible. The skills of generating realistic data are an essential part of being a database developer. It is important: you need plenty of data of exactly the right type, size and verisimilitude

2024-07-01

External Article

What is subsetting, what are the advantages, and how does it make test data management easier?

  • Article

As data grows and databases become larger and more complicated, data
subsetting provides a method of working with a smaller, lighter copy of a
database to make development and testing faster and easier.

In this article, James Hemson poses the questions; what exactly is data subsetting, how and why are developers using it – or not using it, and
what’s prompting conversations about it?

2023-12-11

SQLServerCentral Editorial

Creating Test Data

  • Editorial

This editorial was originally published on Jan 9, 2020. It is being re-run as Steve is out of town. Test data is hard to come by, and I agree with Brent Ozar: " I get so frustrated when I hear trainers/presenters/bloggers/idealists talk about how developers should be using purpose-built-from-scratch data sets with no real customer […]

(1)

You rated this post out of 5. Change rating

2023-06-07 (first published: )

490 reads

Blogs

Advice I Like: Art

By

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

By

One feature that I have been waiting for years! The new announcement around optimize...

Performance tuning KubeVirt for SQL Server

By

Following on from my last post about Getting Started With KubeVirt & SQL Server,...

Read the latest Blogs

Forums

The AI Bubble and the Weak Foundation Beam

By dbakevlar

Comments posted to this topic are about the item The AI Bubble and the...

data type gets lost in data flow

By stan

Hi, in a simple oledb source->derived column->oledb destination    data flow, 2 of my...

i noticed the sqlhealth extende event is on by default , so can i reduce

By rajemessage 14195

hi, i noticed the sqlhealth extended event is on by default , and it...

Visit the forum

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;
go
Then, 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