.git my source

I use git for source control and keep a mainline on github.com.  I created 4 repositories: a Linux CLI for the Sql Server on Linux CTP;  a javascript query Houdini for testing, evaluation and transfer of data between NoSQL or SQL storage platforms; a highly available T-SQL encryption key manager; and an ADO.NET enterprise source control manager for M$ SQL Server that uses M$ SQL Server to store the repo.

sqlpal – a node server CLI for the Docker Contained SQL Server for Linux CTP. Supports installation, configuration, updates, monitoring, troubleshooting as well as DDL, DML, DBCC and dmvs. No Windows client OS necessary anywhere. Install node.js and Docker and these scripts on the 64 bit Linux OS of your choice, NPM install to get the package dependencies, and away you go…

whozurdata

 

 

whozurdata – a node server app domain object maps to and syncs with as many storage engines as you configure. Migrate, replicate, distribute data across the domain among the different data models. Administrative console runs in the browser. Decent way to see how different data stores work with a particular data load anyway.

 

 

Encryption Hierarchy Administration – A secure hub & spoke T-SQL HA/DR key and certificate backup/restore schema. Every SQL Server Instance has at least one key – the Service Master Key -that should be backed up and stored in a safe local location for immediate recall if needed and in a safe offsite location for other HADR scenarios. Maybe for that one key you do not need the overhead of an administrative schema, but using a standard method to backup all Master Keys and Certificates can more easily be automated, mirrored, replicated or periodically copied to an offsite location.

SQLClue A multi-target SMO (VB.NET) change monitoring tool for SQL Server DDL and configuration. Maintain a version-ed near-time (Event Notification + Windows Service) archive of configuration and DDL changes on all SQL Instances in an environment and compares of archives between environments. I ripped out all the licensing code and made this old project open source.

A client side schema compare capability is included in SQL Clue. There are already enough ways to compare T-SQL. SQL Clue’s is the only one available that can compare T-SQL source and Server configuration stored in the SQL Clue repository with objects in a database or script files in the file system. Consequently, this compare tool also excels in scenarios where the SQL instances to be compared cannot directly connect one to the other without compromising either system. The ability to compare configuration properties in addition to script-able objects is also unusual – and handy. As is the ability to select previous versions from the archive for comparisons. As far as identifying differences, this one is as good as most.

The Configuration & DDL Archive proper provides a complete and version-ed audit trail of changes. The UI features a click-through +drill-down ReportViewer (Reporting Services without the service) view every version of every change that emits a SQL Server EVENTDATA  combined with an optional scheduled pull

Most DBAs readily see the utility of the Compare and Archive components of SQLClue. The value of the Runbook is not as obvious. The tool requires a visionary.  The concept is also seen in System Center 2012’s Orchestrator. However the information sharing aspect of meeting SLAs is at the forefront in SQLClue while automation is featured in Opalis. SQLClue is focused on data and Opalis is focused on infrastructure.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s