posted on Sunday, July 17, 2005 1:40 PM by Knight_Reign

User defined transaction scope...

Way back when we were designing the SSIS runtime and had come up with the notion of containers, I was very excited about a concept called User Defined Transaction Scope. To understand why this was exciting to me, you probably need to know what the transaction story for DTS was. Basically, one transaction for a package and only one. Either tasks were in that transaction or not. No subpackage transaction carry over to parent packages.

This was a bit inflexible and we wanted to provide a way to have multiple transactions per package if needed and also have sub package transaction carry over. User defined transaction scope gives a extremely flexible and visibly simple ability to define what's in a transaction and what's not in it.

Well, Jamie Thomson gets it. He's one of the handful of people so far, at least in my book, that has really glommed SSIS. His transaction post explains the concept well.

http://blogs.conchango.com/jamiethomson/archive/2005/07/13/1792.aspx

http://www.sqlservercentral.com/columnists/jthomson/transactionsinsqlserver2005integrationservices.asp

Nice post Jamie.

Universe.Earth.Software.Microsoft.SQLServer.IS.KirkHaselden

Comments

# re: User defined transaction scope... @ Sunday, July 17, 2005 7:01 PM

Kirk,
As always, I really appreciate the comments.

However, my girlfriend Helen has one question. What on earth does "glommed" mean? :)

-Jamie

Jamie Thomson

# Glommed... @ Sunday, July 17, 2005 8:58 PM

Hmmm, glommed...

Glom, to glom... Well, nevermind. A look at Dictionary.com confirms it's actually a word anyway...

glom ( P ) Pronunciation Key (glm) Slang
v. glommed, glom·ming, gloms
v. tr.
--->To seize; grab.<---
To look or stare at.

v. intr.
To seize upon or latch onto something: “The country has glommed onto the spectacle of a wizard showman turning the tables on his inquisitors” (Mary McGrory).

n.
A glimpse; a look.

Knight_Reign