Skip to main content

Learn by sharing

SQL Saturday #40 in South Florida recap.

Speaker dinner was great at Longhorn Steakhouse.  Thanks to Confio Software and for picking up the dinner and bar tab. Great to meet more SQL Tweeps in person and catch up with previous acquaintances.

Evidently, the organizers did a fantastic job marketing this event because there were a large number of attendees.  The numbers I heard were in the 400 - 500 range. Rooms were full for the talks I saw and the Commons was busy.

Check-in was very smooth.  Speaker room was great.  Plenty of water, refreshments, and food for the attendees.  Technical support from DeVry University staff was very helpful.

The PowerShell room was packed for my first session at 8:30 am on "Why DBAs Should Learn PowerShell".  I think I may retitle this "Why ANYONE Can Learn PowerShell". 

My second session on how to automate database login administration and compliance reporting was also well attended.

Had a great time eating a super lunch from Jason's Deli in the speaker room.  Showed @BrentO and Tim Ford(@sqlagentman) my slides from my first deck. I was inspired by Brent's post on how to find great photos for your slide decks.  Got to see Brent speak in person for the first time.  Smooth as silk he was. Even when the power blinked out at the perfect moment in his talk on DR.  

I still picked up a few tips on DR and Virtualization despite him saying it was a 100 level talk.  He provided guidance on size thresholds for virtualization candidates and he confirmed my thinking on the best HA/DR options for SQL Server.

What makes a SQL Saturday great?  Everyone who pitches in from the community.  

Great job by the organizers, sponsors, and speakers for this event! Awesomesauce all over this event.


  1. Hey Now RonDBA,

    Nice post read every word! Nice to meet you, it sure was a stellar event, hope to see your session @ a future event.

    Thx 4 the info,


Post a Comment

Popular posts from this blog

Modifying Endpoint URLs on Availability Group Replicas

I recently had to modify the Endpoint URLs on our SQL Server Availability Group replicas.  The reason for this blog post is that I could not answer the following questions: Do I need to suspend data movement prior to making this change?  Would this change require a restart of the database instance? I spent enough time searching on my own to no avail that I tossed the question to the #sqlhelp hashtag on Twitter and Slack but didn't get an answer prior to executing the change request. After reading the relevant documentation, I think it's probably a good idea to suspend data movement for this change. The T-SQL is straightforward.  USE MASTER GO ALTER AVAILABILITY GROUP [AG1]  MODIFY REPLICA ON 'SQL2012-1' WITH (ENDPOINT_URL = 'TCP://'); ALTER AVAILABILITY GROUP [AG1]  MODIFY REPLICA ON 'SQL2012-2' WITH (ENDPOINT_URL = 'TCP://'); ALTER AVAILABILITY GROUP [AG2]  MODIFY REPLICA ON 'SQL2012-1

PASS Summit 2012 - Gone to the mountain and returned wiser I began my conference schedule by attending Allen White's pre-con "Automating SQL Server with PowerShell". Allen starts by telling everyone in attendance “We all can learn something from each other.  We all know something that someone else doesn't.” I thought this was a great intro and inspiration to the attendees to participate in the PASS Community. Later in the day while answering a question, Allen tells us he is not a PowerShell expert.  Which kind of surprises me.  He says he’s just figured out how to use PowerShell with SQL Server. I think he is being a bit too humble.   Afterwards, I talk to Allen about a script I’m working on and he points me in a direction that hopefully will help me finish it. All in all, it was e xcellent day of training on using PowerShell with SQL Server. As the main conference began, I tweeted about how tight the seating was in some of the rooms on the first day of the main conference.   After the Sum

PowerShell: Quick SQL Server Version Check

I have to keep track of our SQL Server version inventory.  The goal is to reduce the SQL Server 2000 population as fast as possible. The following PowerShell script will produce a csv file containing the database server name and the version of SQL Server it's running. 1: ## Get SQL Version installed on multiple servers ## 2: ## ./sqlver.ps1 3: $start = get-date 4: write-host "Start: " $start 5:   6: [reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo") | out-null 7:   8: $FilePath = "C:\Output" 9: $OutFile = Join-Path -path $FilePath -childPath ("SQLVersions_" + (get-date).toString('yyyyMMdd_hhmmtt') + ".log") 10:   11: # Version inventory 12: @(foreach ($svr in get-content "C:\Input\AllLOBServers.txt") 13: { 14: $s = New-Object "Microsoft.SqlServer.Management.Smo.Server" $svr 15: $s | select Name, Version 16:   17: }) | export-csv -noType $OutFile 18:   1