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

PASS Summit 2012 - Gone to the mountain and returned wiser

http://t.co/pmhsJ3rr 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