Showing posts with label sqlserver. Show all posts
Showing posts with label sqlserver. Show all posts

Jun 14, 2012

Working hard versus working smart

comment on this

It isn’t every day that I get one of those moments of clarity. (Actually, if you’re a recruiter/interviewer reading this, that’s just narrative hyperbole! I get epiphanies, like, hourly. Yeah. Hire me.)

I’ve been tasked lately with some rather… interesting… problems at work. Really the circumstances around them drive me nuts and will have me bald from ripping my hair out but I can’t and won’t get into that here. I’m having to generate a lot of records to be imported into this other system as a sort of systems integration thing. Due to the fundamental differences in their database structures, it involves a lot of redundancy.

It also involves a lot of Cartesian products. What we would normally implement as a pair (or more) of drop-down lists to pick from we’re having to store as related elements. Allow me to illustrate with a contrived example.

Feb 20, 2012

SQL Server Change Data Capture Functions Returning Nulls

comment on this

So we’re trying to set up Change Data Capture on our SQL Server database for one of our projects. The MSDN articles made it seem super simple to set up: just run a couple of stored procedures on your database and they do the work of creating schemas, system tables, and other functions for CDC use. Simple!

We made a few changes to data, noted the entries made in the capture instance tables, and naively thought everything was going fine. Called cdc.fn_cdc_get_all_changes_<capture_instance> and got back… nothing. Just a bunch of null values. Wha…?