I really like building things. Below you’ll find some of the projects I’m involved with. Most of these are tools that I use that help me diagnose issues but others I do just for fun.
This script helps SQL Server users simplify database schema investigation and apply some data profiling techniques. From one simple command this script allows the user to show the schema of any table including indexes and foreign keys, get detailed statistical information on any column in a table, determine the feasibility of a candidate key, and show the distribution of values in a column. I personally use sp_DataParser freqently. I’d much rather type a command than scroll and click in the object browser or use an external tool.
SQL Server Data Dictionary
Often when I walk into a company for the first time this is the first thing that I run. I need to get an understanding of the database schema including indexes, foreign keys, partitions, and views. This Reporting Services project allows me to export a point-in-time look at the database schema. I ran this recently for a client and was able to quickly point out duplicate indexes that needed to be deleted. This also serves as valuable documentation for project deliverables.
Visit SQL Server Data Dictionary on GitHub | Download Sql Server Server Data Dictionary.zip file
SODDI is the StackOverflow Data Dump Importer. Did you know Stack Overflow and it’s sister Stack Exchange sites periodically releases their data in XML files? This is fantastic demo data. This is where SODDI comes in. SODDI takes the XML files and loads them into a database. This tool was orginaly open sourced and abandoned but thanks to Jeremiah Peschka development has picked up once again. I’ve contributed some code already and looking to adding some new features.
Shindy is a web application that is being built by some folks at dotNet Miami. We intend to use it for the dotNet Miami website but we’re hoping that other technical communities would find it useful enough to use it too. Our secret goal is to have it work for larger events,such as Code Camps, as well. When finished it will be Azure compatible with an API. I’m in charge of all of the data related stuff: data model, database deployment, entity objects, etc. I’m really looking forward to seeing how this turns out.
This is a utility that I built that takes the dotNet Miami event.js JSON file to load the dotNet Miami events into the Shindy SQL Server database. It uses the Shindy Entity Framework objects in order to load the dotNet Miami data. This was a project that I created in order to just move the data. It’s definitely not the fastest way to get the data into SQL Server but there’s less than seventy events in the JSON file so it was good enough.