sqlpal – CLI for Developers and Testers that need to run a network of Docker Contained SQL Server for Linux 2017 instances on their Linux desktop. Supports installation, configuration, updates, monitoring, troubleshooting as well as DDL, DML and DMVs. Add, modify or remove databases or the SQL Servers running in containers on the localhost.
Use as easily as a command line query interface featuring fully editable multi-line query batch processing, as a not-globally-installed server host for the excellent sqlpad Chromium browser based query interface – and as a terminal tool in Microsoft’s SQLOPS or even the VSCode IDE. The vi editor is the default source and buffer editor mostly because it is incredibly fun, but also because it works better than anything else with bash in a terminal and is always already installed. Simple configuration update will change the query batch cache editor to most any text editor and another can change the inline source and text file editor to most any IDE. I favor emacs for buffers use the atom IDE for source/script editing.
Connects to SQL Servers over the v-LAN to better simulate a live environment and simultaneously via a sqlpal assigned host port for simplified conveyance of backups and cryptographic artifacts among the SQL Instances and the CLI via symbolic links into Docker Volumes.
No Windows client or server OS used or required. Install node.js, Docker, optionally the mssql-tools, and the source scripts in their own folder on a 64 bit Linux OS, run NPM install in the source folder to fetch the package source dependencies, review the added code base(recommended) and off you go…
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.