Skip to main content

PASS Summit Day 1

Started the day off great with breakfast in the Daily Grill with @BrentO after he tweeted that he had three open spots at his table.  Can't let the dude eat breakfast alone.

I attended these sessions on Day 1 of SQL PASS.  Made it through the day with minimal impact from jet lag.

DBA283S "Virtualization and SAN Basics for DBAs" with Brent Ozar.
This man has a gift for imparting information in a funny and entertaining way.
Great stuff I can use to better understand what is happening at my workplace with links to even more information at his blog under his SAN and Virtual tags.
This one was voted most popular yesterday so it's today's Second Chance session. 

AD314 "Database Testing Overview" with Buck Woody and Alex Kuznetsov.
Buck and Alex gave an overview for properly testing a database before deploying new features.  Buck said Microsoft got one of its biggest black eyes from a one line change that had only one word changed.  Wow! You have been warned, test before your production deployments.

DBA448M "Si Se Puede! Achieving Separation of Duties with SQL Server"
Great session by Lara Rubbelke and Il-Sung Lee that introduced the new Codeplex project SQL Server Separation of Duties Framework.  This will be the first thing, I start exploring when I get back to the office.  Downloaded it last night to my laptop.  

PD193S "You're Not Attractive -  But Your Presentations Can Be"
My favorite session of the day!  This session was probably in a room that was the farthest from the main hub of the conference.  Commented on that when I entered the room and @BuckWoody called me an old man for the rest of the hour.  If he insults you, it's only because he loves you.

I'm a FIRST TIMER at the PASS Summit but I don't feel like one because of my participation in SQL Saturdays and Twitter. Glad I ordered the conference DVDs. Too many great sessions to attend all of them.  I think you don't get the FULL value of this conference without purchasing the DVDs. 
A great start to my week.


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