Skip to main content

February was busy but good...

February was very busy because I had to prepare for my 18th SQL Saturday, prepare abstracts for the 2016 PASS Summit Call for Speakers and keep up with big things happening at work. <Cue sad violin music...>

I submitted two sessions for SQL Saturday Tampa and ended up giving both of them. One in the morning and one in the afternoon. 

My morning session on Monitoring and Alerting for an Azure PaaS Application earned me Speaker of the Month from The Scary DBA and PASS EVP Grant Fritchey. I truly appreciate his recognition and feedback. I WILL incorporate it in future sessions.

In the afternoon, I did a session on how to lock down SQL Server so that DBAs don't have unfettered access to business data. This makes your Compliance staff smile, trust me. 

After SQL Saturday was the final push to get my abstracts done for the 2016 PASS Summit Call for Speakers. They were due the Wednesday after the Tampa SQL Saturday. Do you now understand why February was busy? I submitted four abstracts for consideration for this year's PASS Summit. Two were technical and two were professional development.

Allen White always starts his talks with a little blurb about how we all know something that we can teach others to encourage new speakers.To prove that point, this guy asked me questions via Twitter about my security session. I got a huge kick out of someone with such a stellar reputation score on dba.stackexchange.com asking me for help.

Finally, I've joined my company's Toastmaster club in the hope that it will improve my speaking skills for future PASS events.

Whew! 


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

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