Integration Services Programming Overview

SQL Server Integration Services has an architecture that separates data movement and transformation from package control flow and management. There are two distinct engines that define this architecture and that can be automated and extended when programming Integration Services. The run-time engine implements the control flow and package management infrastructure that lets developers control the flow of execution and set options for logging, event handlers, and variables. The data flow engine is a specialized, high performance engine that is exclusively dedicated to extracting, transforming, and loading data. When programming Integration Services, you will be programming against these two engines.
Integration Services architecture

In this article, we will first illustrate how to create, save and execute SSIS packages using ManagedDTS in C#, then we will do a small comparison with Biml.

Why I No Longer Use MVC Frameworks

The worst part of my job these days is designing APIs for front-end developers. The conversation goes inevitably as:
Dev – So, this screen has data element x,y,z… could you please create an API with the response format {x: , y:, z: }
Me – Ok
I don’t even argue anymore. Projects end up with a gazillion APIs tied to screens that change often, which, by “design” require changes in the API and before you know it, you end up with lots of APIs and for each API many form factors and platform variants. Sam Newman has even started the process of institutionalizing that approach with the BFF pattern that suggests that it’s ok to develop specific APIs per type of device, platform and of course versions of your app. Daniel Jacobson explains that Netflix has been cornered to use a new qualifier for its “Experience APIs”: ephemeral. Sigh…

A successful Git branching model

If, however, you are building software that is explicitly versioned, or if you need to support multiple versions of your software in the wild, then git-flow may still be as good of a fit to your team as it has been to people in the last 10 years. In that case, please read on.

JET Blue? JET Red? oder doch Extensible Storage Engine (ESE)?

Extensible-Storage-Engine – A Non-SQL Database Engine

The Extensible Storage Engine (ESE) is one of those rare codebases having proven to have a more than 25 year serviceable lifetime. First shipping in Windows NT 3.51 and shortly thereafter in Exchange 4.0, and rewritten twice in the 90s, and heavily updated over the subsequent two decades after that, it remains a core Microsoft asset to this day.

The ESE is open source:

Is this the JET database / engine?

No. Well … it depends … the question is not quite correct. Most people do not know that JET was an acronym for an API set, not a specific database format or engine. Just as there is no such thing as „the SQL engine“, as there are many implementations of the protocol, there is no „JET engine“ or „JET database“. It is in the acronym, „Joint Engine Technology“. And as such, there are two separate implementations of the JET API. This is the JET Blue engine implementation, see Notes in here. The origin of the colors have an an amusing source by the way. Most people think of the „JET engine“ as JET Red, that shipped under Microsoft Access. This is not that „JET engine“. We renamed to ESE to try to avoid this confusion, but it seems that the confusion continues to this day.

JET Blue (ESE)


Martin Fowler – Software Design

Kent Beck is an American software engineer and the creator of extreme programming, an original signer of the Agile Manifesto, and the author of the Extreme Programming book series, and a proponent of Test-Driven Development

Developer and Power Users Tool List for Windows


robocopy <source> <target> /MIR /sec /XD "<exclude folder>" /MT /NP /DCOPY:T /COPY:DT

/COPY:copyflag[s] :: what to COPY for files (default is /COPY:DAT).
                      (copyflags : D=Data, A=Attributes, T=Timestamps).
                      (S=Security=NTFS ACLs, O=Owner info, U=aUditing info).

/DCOPY:T :: COPY Directory Timestamps.

The History of Development of Norton Commander

Norton Commander for DOS is the original line of Orthodox file managers that exists in five major versions: 1.0, 2.0, 3.0, 4.0 and 5.0. Only the last one has an additional sub-version (nc 5.5). All versions are still used (mostly by DOS enthusiasts) and are often posted on the abandonware sites. […] It was probably one of the most popular file manager of the DOS era, which along with Xtree remains one of the few programs which managed to transcend their DOS roots and Norton Commander descendants (OFM managers) now exist on all popular OSes. The first version of NC (1.0) was designed and written by John Socha in 1984-1989. We provide a short biographical notes about him later in this chapter.