Skip to main content

PASS Summit Final Thoughts

I've got to figure out how to get to the PASS Summit every year!  It was AWESOME!

It was great to meet more of the tweeps I follow and reconnect with those that I've met before.
It was my first time to Seattle also.  The weather was better than expected. I had a great time walking around the city when time allowed. I also had the opportunity to try the local restaurants and visit the Space Needle.  Everything was great.  Especially the coffee at Top Pot Doughnuts.

Every time slot had several sessions I wanted to attend. You can't get to all the sessions you would like so buying the Conference DVDs is a must.  

Participating in my local PASS user group, SQL Saturdays, and Twitter made being a FIRST TIMER at this year's PASS Summit a non-issue. I did not feel like a FIRST TIMER. I knew a lot of people because of participating locally.  I just blended right in, had fun, and learned a ton.

Being a FIRST TIMER, I didn't realize I could download the slide decks before the DVDs arrive. A prompt from a co-worker made me aware of this benefit.  I downloaded over a dozen decks so far and reviewed them.  Great benefit. Still tons more to go through.

So, the most significant takeaways for me:
  1. Meeting Ola Hallengren and Paul Randal. Talking to them about Ola's Maintenance Solution was invaluable.
  2. The changes to the MCM programming have me thinking about making it a 2011 New Year's resolution. I'll have a post on that later.
  3. The Separation of Duties Framework that Lara Rubbelke and ll Sung Lee debuted has me thinking how to use it back in the real world.
Suggestions for next year:
  1. Any possibility of getting Youtube videos on the conference DVDs for the Top 10 highest rated sessions?
  2. Put Twitter handles on the conference badges.
  3. Select one of my speaker abstracts.  ;-)
I've told my manager that we should be sending a representative every year. No excuses.
I had a great time at my First PASS Summit! 


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

Set Azure App Service Platform Configuration to 64 bit.

If you need to update several Azure App Services' Configuration to change the Platform setting from 32 bit to 64 bit under Configuration | General settings, this script will save you about six clicks per service and you won't forget to press the SAVE button. Ask me I know. 🙄 Login-AzureRmAccount Set-AzureRmContext  -SubscriptionName  "Your Subscription" $ResourceGroupName  =  'RG1' ,  'RG2', 'RG3' foreach  ( $g   in   $ResourceGroupName ) {       # Set PROD slot to use 64 bit Platform Setting      Get-AzureRmWebApp  -ResourceGroupName  $g  | Select Name |  %  {  Set-AzureRmWebApp  -ResourceGroupName  $g  -Name  $_ .Name  -Use32BitWorkerProcess  $false  }       # Set staging slot to use 64 bit Platform setting      Get-AzureRmWebApp  -ResourceGroupName  $g  | Select Name |  %  {  Set-AzureRmWebAppSlot  -ResourceGroupName  $g  -Name  $_ .Name  -Slot  "staging"  -Use32BitWorkerProcess  $false  }  }

Convincing DBAs to Learn PowerShell

Currently, I am the sole DBA at my employer to dive deep into Microsoft Windows PowerShell. It has become my most important tool for discovering the state of our database server inventory as we work towards our standardization goals. It is also the main tool I use to answer questions about the inventory that require querying multiple servers. As I have learned how to use PowerShell, I have shared scripts and one-liners with my co-workers for the past year or more in an effort to convince them it is worthwhile to learn. I've written a couple of articles at Simple Talk describing some of my scripting experience. I've shared links to blog posts, articles, and tips on how to use PowerShell. It got me thinking about what is the best way to get someone started with PowerShell. In my efforts to learn PowerShell, I was always looking for examples. In my opinion, this is the best way to start after some initial readings on the PowerShell basics. So, my latest recommendat