Speaking at SQLBits

I got an early Christmas present this year, I found out I had been selected to speak at SQLBits!  That’s what I call a gift that keeps on giving.

I have always wanted to attend SQLBits so I decided that 2019 would be the year I would finally attend.  Since I had decided to attend, I thought, “what the heck, why not submit session?  I’m going to be there anyway.”  But never in my wildest dreams did I ever expect to be selected.  I will be presenting my Profiling Your Data session.

It’s been twenty years since I was in England and I am super excited to be going back.  I have family ties to England so I added a few extra days for sight seeing.  Last time I was there I visited Malvern Link, home of the Morgan Motor Car Company, my dad’s favorite auto manufacturer.   This time I am planning a quick trip over to Liverpool so I can see where my Dad’s favorite band (and one of mine) was started, you may have heard of them, they’re called The Beatles Winking smile

Speaking at SQL Saturday Nashville

I am excited and honored to announce that I have been selected to speak at SQL Saturday Nashville on January 12, 2019.

I’ve been to Nashville before, in fact I was just there last June for Music City Tech, and am super excited to be going back.

I will be presenting my Profiling Your Data session.  If you’re in area and haven’t registered yet, there are still seats available, you can register here.

Feel free to stop by and say, “Hi”, I’d love to see you.

Where to Store Index DDL

Recently I was asked my opinion, via Twitter, on where to store the index DDL for a single database that had multiple clients with varied usage patterns.  You can see the whole thread here.

It’s a great question and there were some interesting suggestions made.  My approach to this scenario is kind of a hybrid of all the suggestions and comments.

I’ve had to deal with this kind of thing in the past and what I found worked best is to create a single file for each client that contains the client specific DDL.  I wish I could take credit for this idea, but it wasn’t mine, it belonged to a co-worker.  At first I resisted and thought it was a bad idea.  I mean really, mixing DDL for more than one object in a single script just seemed wrong and goes against every fiber of my OCD organizational self.  But in the end, this is what worked best in our environment.

Our initial thought was to include our index DDL with the table, but use variables to name the index objects that were specific to the client.  This way the index names would never collide, but then that kind of defeated the whole purpose of different indexing strategies for different clients.  Thankfully we scrapped that idea before we implemented it.

We tried creating separate files for each table that had client specific DDL in each file.  That became a nightmare when it came time to deploy and maintain.  We had to build logic in our pre & post deployment scripts to handle that.

Then we tried separating the index DDL files out by client, so we ended up with a bazillion index DDL files for each table.  Okay, may not a bazillion, but it was a lot and it was even more of a nightmare to maintain.

We settled on the approach I mentioned earlier, one DDL file per client that held all the DDL that was specific to the client, not specific to any object.  We found it was much easier to maintain and deploy.  We defaulted each of our client specific DDL files to be NOT included in the build.  When it came time to do a build/deploy for a specific client, we would set the option to include the client specific file in the build.  We were not using continuous integration, so this may not work if that is what your shop is doing.  Or it may work with just a few tweaks to your process.  It did work for our situation and it worked well.

I don’t think there is a single correct answer to this question.  Like almost everything else in our tech world, the answer is going to be, “it depends”.  Figure out what works in your environment and then go with it.  It might take a few trial and error runs to get it right, but you’ll figure out what works best over time with a little persistence.

I’d love to hear your thoughts on this.

Speaking At SQL Saturday DC

I am so excited to announce that I was selected to speak at SQL Saturday DC on December 8, 2018.

I will be presenting two sessions, What is Power BI? and Data Types Do Matter.  My Data Types Do Matter session is the same session that I presented at PASS Summit 2018, so if you couldn’t make it to PASS Summit this year, now’s your chance to see it.

If you’re in the Washington DC area on December 8, 2018, register for SQL Saturday DC and stop by and say, “Hello”.  I’d love to see you.

Speaking at SQL Saturday Oregon

I am so excited and honored that I have been selected to speak at SQL Saturday Oregon on November 3, 2018.

I will be presenting my Data Types Do Matter session at 10:15 am.  I am so excited to be presenting to a kind of “home town” crowd.  I lived in the Willamette Valley for a while when I was a kid and even graduated from High School out there. 

If you’re in the Portland area on November 3, 2018, stop by and say hello, I’d love to see you!

Things To Know About SQL Saturday Charlotte #806

Did you know that SQL Saturday Charlotte is just a few weeks away on October 20, 2018?  This will be the seventh year for SQL Saturday Charlotte.  Here are a few things we think you should know.

What’s New

Venue

After being at the same venue for the last six years, we decided to switch to a new venue this year.  We will be at the Central Piedmont Community College – Harris Campus, located at 3210 CPCC Harris Campus Dr, Charlotte, North Carolina, 28208.  This is on the opposite side of town from our previous venue and very close to the airport.

Pre-Cons

We have not one, not two, but THREE pre-cons to choose from this year!  Whether you are in the DBA or BI realm, there’s something for you!  Check them out, but register soon as seats are limited.

Devin Knight & Mitchell Pearson

Kevin Kline

Kevin Feasal

Technology Workshops for Kids

We are offering two workshops for kids.  A morning session for kids aged 7-10 and an afternoon session for kids aged 11-13.

Morning Session – Kids aged 7-10

Afternoon Session – Kids aged 11-13

Organizing Crew

We have had some excellent volunteers in the past.  So excellent in fact, that we decided to add them to our organizing team.  Please welcome Brad Llewelyn (B | T) who is acting as our PM.  He’s doing a great job, considering it’s akin to herding cats.

Recommended/Discounted Hotel

We have worked hard so you can save some green by finding hotel that is close to the venue and the airport.  Use this link to get a discounted rate of $119 per night.

What’s The Same

Organizing Crew

For the last seven years, our core organizing crew has been made up of the (mostly) same great #SQLFamily members.  Because of this we are able to provide a  great experience for attendees, speakers and sponsors.

Our Commitment

We work hard to select the sessions that will provide the best range and depth of learning for our attendees at the same time helping first time speakers get their start.

We hope to see you this year at SQL Saturday Charlotte on October 20, 2018.  If you haven’t registered yet, do so soon, our new venue is smaller and we will have a registration cap this year.

Moving On To New Adventures

I am pleased to announce that as of September 10, 2018, I will be part of the SQL Data Partners team!

I started my career at a consulting company in Denver, CO right out of college and loved the challenges that it brought.  After a long hiatus from consulting, I’m headed back to my professional roots and couldn’t be happier.

I will be working with Carlos Chacon (In | T), Managing Partner & Bill Lund (In | T) and I can’t wait to get started.  If you aren’t familiar with Carlos, you should be.  He has a great Podcast and runs an excellent conference called SQL Trail.

Here’s to new adventures.