There is an ongoing deployment-gone-wrong story involving SQL Server and about which I have heard nary a word on the SQL Server blogs. While it looks a lot like a classic, doomed-to-failure approach to deployment, surely there are lessons to be learned somewhere.
The Proximity project is coming along. I have successfully loaded a large family tree from a GEDCOM file and a very large set of pedigrees downloaded from Ancestry DNA using DNAGedcom.com. Name, place, and date parsers are working reasonably well, although there is considerable room for improvement. I have been doing a great deal of refactoring as I discover, bit by bit, how to usefully apply a relational database system to solving difficult genealogical problems.
Update (7/25/16): You should be fine with older versions of Report Server and SSMS 2016/Visual Studio 2015/SSDT, if you do these three things: Set the appropriate compatibility level for deployment (TargetServerVersion) in the report project properties. Build the report project before deploying (this may also catch some kinds of errors). … Continue reading →
119 SQL Code Smells.
Herding Cats: The Myth of Incremental Development.
The Curse of the Excluded Middle – ACM Queue.
Cursor-Killing: Retrieving Recently Modified Data – SQLServerCentral.
What is DevOps really?.
Branching and Merging: Ten Pretty-Good Practices.
…for the sake of the argument, can we agree that stress and insanity are bad things? Awesome. Welcome to programming. via Programming Sucks.