Kathi Kellenberger

Kathi Kellenberger is a Sr. Consultant with Pragmatic Works. She is an author, speaker and trainer.
  • Interests: Walking, running, grandchildren!

All authors

SQLServerCentral Article

What's new with SSIS?

With the release of SQL Server 2005, there have been many changes in the product, but probably none as dramatic as the changes to the ETL tool. Data Transformation Services has become SQL Server Integration Services, or SSIS. It has been completely redesigned with a whole new paradigm for developing data movements. Kathi Kellenberger brings us a short introduction to this new tool.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(3)

You rated this post out of 5. Change rating

2006-01-31

20,896 reads

All authors

Blogs

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,...

T-SQL Tuesday #193 – A Note to Your Past, and a Warning from Your Future

By

I haven’t posted in a while (well, not here at least since I’ve been...

Read the latest Blogs

Forums

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...

New-AzSqlInstanceServerTrustCertificate - Failed and no clues

By BrainDonor

Using New-AzSqlInstanceServerTrustCertificate to import a certificate and get the message New-AzSqlInstanceServerTrustCertificate: Long running operation...

Refactoring SQL Code

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Refactoring SQL Code, which is...

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