#CareerAdvice from a friend

My friend Steve Jones posted a couple of career-oriented articles on his ‘blog that caught my attention, and I figured they’d be helpful for people possibly looking to make career adjustments. I thought they were worth passing along.

First, Steve talks about job satisfaction. Is your job or career fulfilling to you? Do you enjoy working a hundred hours a week, or would you rather work fewer hours for less pay but manage to balance your work and your life? While Steve’s article doesn’t necessarily answer those questions outright, it does make you think, and I think a number of people can benefit from his thoughts.

Second, he also mentions an offer by Andy Leonard. In an effort to help those who are recently jobless due to the COVID-19 crisis, he is offering free training to those who have lost their jobs. The courses are about SSIS, and you need to email Andy directly to register for the courses (follow the instructions on his ‘blog article).

In that same spirit, while I don’t have wide course offerings I can give, I can provide a link to my online presentation about ‘blogging that I did back in January. I hope you find it helpful.

Installing #SQLServer 2019 Developer on my laptop

A while back, I wrote about installing SQL Server 2016 on my laptop. Since then, Microsoft has released SQL Server 2019. Additionally, I bought a new laptop last November; my tired old HP 4430s had served me well for several years, but it was showing its age, so I decided it was time to upgrade. Since we have updated versions of SQL Server, and I have a (still relatively) new laptop on which to install it, not to mention that I have some time with this COVID-19 isolation, I figured this would be a good time to install SQL Server 2019 on my new laptop.

Before we begin, let me start with my laptop specs. I make no claims that these are the recommended specs for SQL Server, but this is what I have.

  • HP Pavilion x360 Convertible 14m-dh1xxx
  • Intel Core i5-10210U @ 160 GHz
  • 8 GB RAM
  • Windows 10 Home Edition (it’s what came installed)
  • 129GB available disk space

I started by going to the SQL Server downloads page and downloaded the freeware version of SQL Server 2019 Developer. There are a number of versions on this page, including (among other things) a trial version of SQL Server 2019 on-premises and SQL Server 2019 on Azure (and, of course, the Express version of SQL Server). For my rather modest needs, which includes practicing SQL Server skills, writing about it from time to time, and having some fun with it, Developer version should suit my needs.

The link downloaded SQL2019-SSEI-Dev.exe to my machine. I ran the file and was greeted by a screen asking for the installation type.

I decided to use the Custom option. The lazy body in me thought about running the Basic installation type, but since I’m documenting this installation, I figured it would defeat part of the purpose.

The next screen asked where to download the media. By default, it goes to C:\SQL2019. Since most everything I download goes to my Downloads folder, I decided to switch it there. I set it to download to a SQL2019 folder within my Downloads folder. It also indicated that I would need 8.9GB free space, with a download size of 1.4GB. My new laptop doesn’t have the disk size that my old one did, but I still have plenty available, so it shouldn’t be a problem. (One thing I should note: my new laptop uses a SSD, as opposed to the traditional storage disk on my old machine.)

I clicked Install, and the install package started to download.

Once the Installer finished downloading, the SQL Server Installation Center appeared.

I ran the System Configuration Checker, and it came up cleanly. I decided to proceed with installation. I clicked the Installation tab and selected New SQL Server stand-alone installation or add features to an existing installation.

On the Product Key page, I selected Developer under free edition. The next few screens were straightforward — the only warning I saw was for my firewall — until it got to the Feature Selection screen. I went ahead and selected all features, which would take up 14GB of disk space. If you’re installing SQL Server on your own machine, you’ll need to decide what features you want to install at this point.

I went with the default instance for the instance configuration.

I selected standalone PolyBase-enabled instance. I’m using this on a standalone configuration, after all.

Since I don’t have Java installed on my machine, I used the Open JRE included with the installation. If you have Java on your machine, you’ll need to determine what instance of Java you want to use.

Under Server Configuration, I used the default service accounts. There’s a note that reads: “Microsoft recommends that you use a separate account for each SQL Server service.” I am not sure about the implications of using the default service accounts; this would be a question for someone who knows more about SQL Server than I do.

Under the Database Engine Configuration, I went with Windows authentication mode. If I was installing this under any configuration other than my own machine and login, I would not go with this option; I would use Mixed Mode and specify a SQL user account. I added myself (clicking Add Current User) as the administrator for this account. Again, this is not something I, personally, would recommend for a large-scale installation, but since I’m the only one who’ll be using this instance, and I have no intention of using this for anything other than demo, practice, and documentation purposes, I went ahead and used Windows Authentication.

I pretty much went with the defaults for the rest of the installation. I did need to consent to install R and Python. I got to the Ready to Install screen, clicked Install, and let it do its thing.

Installation was straightforward and painless. In years and installations past, I’d be writing about the errors that came up and the number of times I’d have to click or press Enter to continue with the installation, but there were no such prompts. I let it go and went off to do other things. I’m not sure how long it took — I’ll guess around twenty minutes, although it seemed longer — but when I looked again, SQL Server was installed on my laptop.

That was as far as I got for this installation. I still need to tinker with post-installation configurations, including SSMS, SSIS, and any tools that I need to actually do something with SQL Server. That’ll likely come later when I have a chance to tinker some more.

Coming up with ‘blog article ideas

Ever come up with a great topic about which to write an article? Do you have something on your mind that you want to get out of your system? Did you just learn something new and profound? Or is there some topic about which you don’t know but are trying to learn? Did you pick up some useful tidbit that you want to set aside for later use? Did you come across something you want to share?

I could keep going with this, but I’d rather not write a rambling paragraph that will eventually bore you; besides, I think you have the idea. I’d guess that one of the most common questions when trying to write a ‘blog is, “what do I write about?”

For me, personally, a lot of my ideas just pop into my head (including for this very article that you’re reading right now). If I think the idea is profound enough that it might help other people, I’ll start writing about it. Other times, I’ll come up with some idea, jot it down in a post, and save it for later. I have 100+ such draft articles; whether or not they ever see the light of day remains to be seen.

There are a number of things to consider when coming up with draft article ideas (and I dedicate several slides to this very topic in my ‘blogging presentation). If you’re trying to come up with things to write about, here are some thoughts that might help get you going.

  • What’s on my mind? It might sound obvious, but a lot of my ‘blog article ideas come from random thoughts that just happen to pop into my head. They’ll come from random sources — something I’m working on, something I’m watching, reading, or listening to, a question that someone asks, and so on. Every now and then, they’re thoughts that I think might help someone out. That can make great article fodder, so make sure you at least make a note of it. It happens more often that you might think; I’ve surprised myself at the number of ‘blog articles I’ve written that started as just random thoughts in my head.
  • I know something you don’t know — and I’m willing to share! Chris Bell, one of my friends on the SQL Saturday speakers circuit, once told me something profound, and it’s something I haven’t forgotten. He said, “an expert is someone who knows something that you don’t.”

    I’ve been a working professional for a long time now (I won’t say how long!), and I’ve learned a lot in my experience. I think I have some knowledge in at least a few subjects, and what I think can potentially help other people. Helping other people is one of my great passions, and if something that I know helps someone else, then I’ve accomplished something.
  • I just learned something new! Some people seem to have a misconception that you need to be an expert at something to write a ‘blog. Wrong! If you’re learning something new, keeping an online journal about what you learn is one of the best reasons to maintain a ‘blog! You’ll be able to see for yourself just how much you learn. Additionally, if you’re actively seeking new employment, it shows potential employers that you’re learning something, and that you have the ability to learn. Not only that, it shows off your expertise in terms of what you’ve learned. That’s something that hiring managers like to see!
  • I don’t want to forget this. Let me write it down. One of those people you could help is yourself. Matt Cushing tells a story in his networking presentation about the time he was trying to solve a problem, and he found the answer to it… in his own ‘blog! He had written an article about the very thing he was trying to solve, and found the answer in his article that he had forgotten about!

    As Matt says in his presentation, “a ‘blog can serve as your own personal Google.” A ‘blog can serve as scratch notes to yourself, and it might even help others in the process.
  • Bring people in. Don’t drive them away. You want people to read your ‘blog, don’t you? Like anyone else, I have thoughts and opinions about a lot of things, but I won’t ‘blog about a lot of them. I generally avoid any topic that’s divisive. You will almost never, if ever, see me discuss politics or religion on my ‘blog (I despise talking about politics, anyway). If I want to talk about religion, I’ll go to church. If I want to learn about politics, I’ll read The New York Times. Unless your ‘blog is specifically about those hot-button topics, they are more likely to drive people away than bring them in. I will not touch them on my ‘blog.
  • Avoid posting anything that is overly-sensitive or qualifies as “TMI,” unless it’s relevant to your topic. People generally don’t want to hear about your last trip to your gastroenterologist. Stuff like that isn’t typically what ‘bloggers write about. However, if some anecdote comes out of it — “my appointment taught me a lesson that applies to my professional life,” for example — maybe then, it’d be appropriate to write about it. However, be careful about it — make sure that what you write is appropriate for your audience. Nobody wants to read the details of your last trip to the bathroom while you had the bad case of diarrhea.
  • It’s okay to go off-topic once in a while. At the time of this article, Steve Jones of SSC is taking a sabbatical from his job (a nice little perk that he has available to him). During his time away from work, he has been ‘blogging about his daily exploits, which include skiing, learning to play guitar, and working around his ranch. I’ve been enjoying his posts, and I even told him that I was living vicariously through his posts.

    I’ll occasionally post an article that has nothing to do with my job, technical communication, or professional development. I’ll sometimes write about my extracurricular activities — my music endeavors (I play four different instruments), my workouts (I am an active Crossfitter), and so on. If you maintain a ‘blog about professional topics, it’s okay to post something off-topic now and then. It shows you have other interests, and it shows that you have a life outside of work. It shows that you’re human.

There are numerous other ways to generate ideas for ‘blog fodder. Feel free to comment below with your favorites. Hopefully, these thoughts are enough to help you get your own ‘blog going.

Blogging virtual presentation — Tuesday, January 21 @CASSUG_Albany @PASS_ProfDev

On Tuesday, January 21, at noon (US Eastern Standard Time), I will be doing my presentation titled “Blogging for Success: Advancing your career by blogging.”

If you’re interested in starting a ‘blog, I’ll talk about my own experience with ‘blogging and lessons I’ve learned along the way. Some topics I’ll discuss include how I got started, ‘blogging platforms, and subject matter.

For more information and to register for the event, use this link.

Hope to see you there (so to speak)!

Choosing which #SQLSaturday to submit

I saw an interesting (and amusing) tweet from Matt Cushing about applying to three SQL Saturdays in February and questioning his own sanity. Matt, I could’ve told you that you’re insane! 😉

All kidding aside, it did get me thinking: how do I select the SQL Saturdays to which I apply to speak? If you’re a new speaker, this might be a question that you’re considering.

For those of you who may be new to my ‘blog, I’m a regular SQL Saturday speaker. I’ve been speaking at SQL Saturday since 2015. I’ve written before about what to expect at a SQL Saturday, and I’ve even written about some of my experiences traveling to SQL Saturday. So I figured I’d write a primer as to what I consider when selecting where to submit my presentations.

Before I do, however, I should lay out a disclosure. I present at SQL Saturday completely on my own. And by this, I mean on my own time and on my own dime. I don’t do this for pay, and my employer does not dictate what events I attend or where I speak. I do this because I love doing it (and it doesn’t look bad on a resume, either). All schedules are my own schedules, and all expenses come out of my own pocket. My employer does not reimburse me for my trips (some speakers have their companies pay for their trips, but I do not have that luxury). This plays a huge factor into my planning, as you’ll read about below.

Will it break the bank?

Since I mention that I do this on my own dime, I’ll start there.

Cost is a huge factor whenever I consider where to submit. Traveling gets expensive (and traveling also incurs other issues, which I’ll talk about in a minute). The easier it is for me to get to an event, the cheaper it is for me to get there. I apply to nearly all SQL Saturday events that are within easy (about a few hours) driving (or, for NYC, commuting) distance from my home in Troy, NY. I have yet to apply to an event (other than PASS Summit) where I have to fly. There is good reason for that. Flying is neither cheap, nor convenient.

Of course, I apply to speak at Albany every year. It takes me all of twenty minutes to drive from my home to the UAlbany campus, where the event is held. It’s my hometown event, and it’s sponsored by my local user group, of which I’m a member. I am not paying for a hotel, and my trip expenses are no more than my normal commute to work. Other than nominal expenses, I pay nearly nothing to attend this event.

I attend New York City pretty much every year, regardless of whether I’m speaking or not. It’s an easy trip — doable in a day, in fact. Amtrak goes directly from Albany right into midtown Manhattan, making it a very easy trip. If I do need to stay overnight, my siblings live in the City, so I have a place to stay. Or, I might splurge a little for a hotel. New York isn’t the cheapest city to visit, but if you look hard enough, deals can be had.

Boston — straight shot down I-90 for me, roughly a three-hour drive. And while Boston area hotels aren’t necessarily cheap, I can find lodging that won’t break the bank.

I did apply to speak at Chicago this coming year. I created a theoretical itinerary and realized that I could make it work. If I’m accepted, it would represent my first SQL Saturday where it wasn’t feasible for me to drive there.

There are a number of other examples, but at this point, you can see where I’m going with it. Finances will often dictate whether or not I can attend an event. However, finances alone aren’t the only factor. There are other things I need to consider, such as…

How easy is it for me to get there?

One event that I’ve never attended — and would like to — is Cleveland. With its relative proximity to New York State, you’d think that Cleveland would be an easy one for me to attend.

It isn’t.

For starters, Cleveland, for me, is roughly an eight-hour drive… in good weather. Now consider: Cleveland holds their event in February. Imagine trying to make that drive in unpredictable, snowy, winter weather. Maybe I could get lucky and get good weather on a drive out that way, but it’s a crapshoot and not guaranteed.

Okay. Amtrak goes to Cleveland. How about hopping the train?

The Lake Shore Limited, which travels between Boston/NYC and Chicago, makes a stop in Cleveland. Is it a direct line from Albany? Yes. Is it convenient…?

That would be a big no. The train arrives in Cleveland at 3:30 AM. As for the return trip, it departs at 5:50 AM. Either way, it would make for a very inconvenient itinerary.

That pretty much leaves flying. In years past, this would also not have been an option. Flights from ALB to CLE have been expensive and inconvenient. Additionally, there are no direct flights between the two cities. I did look up a theoretical flight for SQL Saturday #930 and found a roundtrip flight as low as $218. I’d have to fly through Detroit to do it.

Maybe I could’ve applied to speak in Cleveland and flown out. But I didn’t want to deal with the hassle.

One of these years, I might be able to make Cleveland work. That day hasn’t yet arrived.

Is the travel convenience (or inconvenience, as the case may be) worth it for a short weekend trip? That’s up to you to decide, but it is another major factor that I consider when I think about submitting to an event.

Does it fit my schedule?

Another event that has interested me is Pittsburgh. I spoke at Pittsburgh in 2016, and it was an enjoyable event; in fact, I’ve been wanting to return ever since. It’s a long drive for me, about eight hours. At the time, it was the farthest that I’d ever traveled for a SQL Saturday (that has since been surpassed by Virginia Beach).

I decided that eight hours is a long time to spend in a car, so I’d prefer not to drive there. It turns out that I can get Amtrak to Pittsburgh, and the schedule works for me. On top of that, I have a friend who lives there, so I’d probably have a place to crash. Pittsburgh is a long trip for me, but it’s one that I can make work.

So why haven’t I been back? Mostly, it’s been because of scheduling issues. One year, I withdrew from Pittsburgh because it was separated by only a week from another SQL Saturday where I was accepted to speak, and I decided that traveling on back-to-back weekends was a bit much. This past year, I’d fully intended to apply… and New York scheduled theirs for the same day. Other years, I’ve had a number of things come up on my calendar that have interfered with the event.

I’ve withdrawn from or didn’t submit to other events because of schedule conflicts. As much as I’d like to submit to every event that’s within a couple of hours from me, it doesn’t always work out.

If I was able, I’d apply to as many SQL Saturday events as possible. However, there’s also something to be said about work/life balance… and maintaining your own sanity.

Summary

So if you’re a road warrior, you like to keep a busy schedule, have deep pockets, or have an employer who will fund your trips, a lot of these issues might not affect you. But for other SQL Saturday speakers (like me), we do this on our own time and our own dime. These are the things I consider whenever I decide whether or not to apply to speak at a SQL Saturday. Whether or not you can handle the issues that come with getting to an event is up to you.

Blogging virtual presentation — January 21

A couple of weeks ago, I mentioned that another virtual presentation was in the works. Well, it’s been scheduled!

I will be doing my ‘blogging presentation at noon, EST, on Tuesday, January 21!

Use this link for more information and to register! Feel free to join me!

Want to learn something new? Get off your butt, and go get it!

A few weeks ago, Monica Rathbun wrote a ‘blog article about pursuing education or learning opportunities. It had been shared and retweeted a number of times by a number of people. I had meant to do the same, but it came out right around the same time that my father-in-law passed away, so the timing was inconvenient for me. After a few weeks of dealing with family issues, not to mention a week away at PASS Summit, my life has settled back into a state of semi-normalcy, so now I can go back to boring all of you with ‘blog articles and posting things I find interesting.

Additionally, Steve Jones came out with an article this morning about the benefits of conferences. Conferences are a great source of learning and networking. Some, such as SQL Saturday, are even free. If you ever have an opportunity to attend a conference or a seminar, I recommend it highly.

People, all too often, make excuses as to why they don’t learn anything new. Monica’s article lists out many of those excuses, and goes on to say why they are all invalid. She goes on to list resources you can use to further your education. It isn’t just about getting a degree or a certificate credential; it’s also about attending conferences and user groups, reading ‘blogs and articles, talking to people and networking, going to your local library, and getting involved with activities. Go read Monica’s article; it’s a great read.

I’ll make another suggestion: consider starting your own ‘blog. One of the best ways to learn about a topic is writing about it, even (and especially) if it’s a topic you don’t know. Writing about something you don’t know is a challenge, and it can sometimes be uncomfortable. But you won’t get anywhere unless you step out of your comfort zone.

Education is important, and we are always learning. Don’t use lack of money or lack of time as an excuse not to learn. There are many learning resources out there that you can do on your own time and require little or no money. If you’re seriously interested in learning about some topic, take the initiative and go get it. Otherwise, you run the risk of remaining in the same routine rut for the rest of your life.