Skip to main content

Finding the next job was easier because...

I am an active participant in PASSSQL Saturday, and Twitter.

Due to circumstances beyond my control, I had to look for a job after nine years at my previous employer.  
The management decided to relocate the IT department to North Carolina. I live in Florida. Neither myself nor my wife were interested in moving to colder climes. 

I posted my updated resume in January 2015. I really started looking seriously at the end of March.

Because of my participation in the Florida PASS user groups, SQL Saturdays, and Twitter, most of my job leads came from people I know. The one job that I did a phone interview for via a recruiter ended up being with someone who had attended the most recent Tampa SQL Saturday and one of his co-workers had attended my session. They wanted to do an in-person interview but couldn't wait until June for me to start. The conditions of my severance package dictated a June start date for the next job.

I had leads from my user group leader, a former co-worker via Twitter, and an MCM who I met via SQL Saturday. I joined Twitter because of a Tampa SQL user group presentation in 2009 given by Jorge Segarra AKA @sqlchicken. Speaking at SQL Saturdays and user groups made interviews a breeze.

I ended up taking the job with the MCM. He is now my manager.  :-D

I start my new job after two weeks vacation.

The point of this post is the transition was MUCH easier than I could have ever imagined because of the participation I've described above.

If you have to find another job, this is the way to do it. Be social. Contribute.


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

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

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