Skip to main content

Didn’t attend SQL PASS? Twitter was the next best thing.

I didn’t attend the 2009 SQL PASS Summit in Seattle  but I am following a bunch of people on Twitter who did.

There tweeting and twitpics were the next best thing. 

The Twitter feed was like a stock ticker that kept me current on what was happening at SQL PASS.

What did I learn via Twitter regarding SQL PASS?

I should get the conference DVDs.

The webcast "Simplify SQL Server Management with DMVs - the Experts' Perspective"  was hilarious.  I attended.  Buck Woody’s reign of humor continued throughout the week.

Louis Davidson (@drsql) loves sys.dm_io_virtual_stats.

I learned a simple query to find all the DMVs on a server from Buck Woody.

I can hover over the columns in Activity Monitor and see what DMV they are from.

Tom LaRock said "You don’t just get me, you get my network."  A great way to justify SQL PASS attendance to a manager.

The Quest Twitter T-shirts were great. 

Never ever walk out of a Buck Woody presentation.

Never bring a MacBook into a room with Buck Woody.

The keynote speeches will be on the DVDs.

One demo had a 192 CPU machine on stage. Wow.

Tweets to the SQL tweeps’ blogs further detailing their experiences.

Go to SQLServerPedia.com for a list of SQL Tweeple or check out my Follow list @RonDBA.

Next year's PASS Summit will be in Seattle from November 8th - 11th, 2010.  $995 rate if you register soon.

Thanks to all the SQL Tweeps for your coverage of SQL PASS last week!.

Comments

  1. Nice recap! I thought the live streamed DMV webcast was hysterical as well. Always cool to see experts who not only love what they do but enjoy being around each other. Seeing the energy of one bounce of another and so on is really cool to witness.

    ReplyDelete

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://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. ;-)