The Oozie coordinator showed green. Every action node in the workflow completed with status SUCCEEDED. The daily aggregation job had run, written its output to HDFS, and Oozie was happy. The output had zero rows. Nobody noticed for four days, because there was no alerting on output volume. The downstream
microsoft sql
Last time I walked you through how to see if your database will work with Windows Azure SQL Database (WASD) using the Migration Wizard on Codeplex. It's an easy
microsoft sql
As promised we're going to dive into the details on how we would actually migrate the database from your on premise server to Windows Azure SQL Database. We're
microsoft sql
How long could your company go if your database server simply stopped? Many of my clients have never even thought about this question. It's a question you need
microsoft sql
My system is down, what do I do? It's unfortunate, but sometimes a company has to experience a complete server failure before I'm invited to help. During these
Windows Azure
Let's continue our discussion on what it takes to migrate a database from SQL Server classic to Windows Azure SQL Database (WASD). At this point in the
A dacpac is a zip file. Inside it: your database schema compiled into a model, and optionally, your reference data. You pass it to SqlPackage.exe, point it at a target database, and SSDT figures out the delta and applies it. This is SSDT's deployment model, and it&
Running tSQLt tests in SSMS is fine when you're developing. But tests that only run when a developer remembers to run them aren't really protecting you. The goal is tests that run automatically on every code change — before the change gets merged, before it gets deployed,
I want to tell you about a pipeline I inherited. It consumed messages from a Kafka topic and wrote structured records directly into an analytics database — no intermediate storage, no raw landing. The producer was an application team in a different department that had, historically, not told anyone when they
I've had this conversation more times than I can count: "We keep our schema in source control." "What does that mean exactly?" "We have a folder with all our CREATE scripts." And then I look at the folder, and it has one
The first time most SQL developers look at Kafka documentation, they hit a wall around partitions. The concept exists in SQL Server too — table partitions, partition functions, partition schemes — but Kafka uses the word to mean something slightly different, and the difference matters when you are trying to figure out
Windows Azure
Last time I introduced you to Windows Azure and some of the key features: pay as you go, scalability, and ease of use. These are the three key points I make