Skip to main content

SQL Saturday #49 - Orlando

My THIRD SQL Saturday of the year is behind me.

I spoke in Tampa #32 and South Florida #40 earlier this year.

Jack Corbett(@unclebiguns), Andy Warren(@sqlandy) and their volunteers did another EXCELLENT job on this event.

What I liked: 

The coverage via the #sqlsat49 Twitter feed.

The constant updates from Jack on the event via e-mail and twitter.

The large schedules on the wall in the hallways even though I stayed in the PowerShell room most of the day.

Liam Fitzpatrick’s Bangers & Mash with Sam Adams OctoberFest beer at Friday night’s speaker party sponsored by Confio Software 

Meeting the ScriptingGuy and ScriptingWife.  Nice people.  Funny guy.

The ScriptingGuy statue that @MaxTrinidad got as a gift. He wouldn’t let me touch it.

I REALLY liked that statue Max.  (c;

Why Learn PowerShell?

The tweet from the @ScriptingGuys while I was doing my session “Why Learn PowerShell” asking if I wanted to do a guest blog post for the Scripting Guy blog.

How about “If the Original Cylons Had Learned PowerShell, Would They Have Been replaced by CGI?”.

Maybe I should have learned PowerShell?

@z_williamson’s tweeting the color commentary for the sessions he attended. Beware don’t make a mistake when he’s in the room. One of the presenters had an incident with a lack of power to his laptop and blurts out “Don’t tweet that!”.  Too late, z_williamson had pulled the twitter trigger well before. I hope he’s going to the PASS Summit to provide coverage. I’d also like to thank him for taking pictures during my sessions.

A few quibbles:

The sponsor area.  Need to find another table arrangement that reduces the bottleneck in the  hallway.

Not enough Ninja T-shirts to go around. Seriously.  LOL. No, I’m kidding.

Moving on…

Hey, Tampa. Let’s do a Kung-fu SQL Saturday in 2011. Orlando is going Ninja next year.

The 2010 PASS Summit in Seattle is next for me. @RonDBA will be there.

I can’t say enough how valuable the SQL Saturday concept is for networking and staying current on SQL Server. If you want to get ahead, you need to attend.

Comments

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://10.10.10.1:5022'); ALTER AVAILABILITY GROUP [AG1]  MODIFY REPLICA ON 'SQL2012-2' WITH (ENDPOINT_URL = 'TCP://10.10.10.2:5022'); 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  }  }

Rediscovering SQL Server Agent Alerts...

Having moved from a Fortune 50 company using BMC Patrol for SQL Server Monitoring to a small software company of less than 200 people, I'm rediscovering SQL Server Agent Alerts. Why might you ask? Because small companies can't afford expensive tools and need to use the out-of-the-box features as much as possible. This past week, I rediscovered that you can alert on SQL Server performance conditions using SQL Server Agent. I needed to alert on database transaction log usage.  How to create SQL Server Agent alerts can be found at the link below. https://msdn.microsoft.com/en-us/library/ms180982.aspx Under Options, I suggest you set a delay of 10 minutes. Unless you like to be spammed every minute when bad things happen. I'm hoping it will provide enough notice to prevent an undesirable event from complicating my life. Do this before your storage runs out of space on a holiday. ;-)