As I wrote earlier, I discovered, much to my chagrin, that I vastly underestimated how much disk space I would need when I purchased my laptop. So I went to Amazon and bought a new 2TB internal SSD for my machine. It’ll take about a week or so to arrive. Until it gets here, I needed to free up some space on my drive.
So, I first went to my Control Panel and looked at uninstalling SQL Server. But when I got there, I saw a number of things under Programs and Features, as you can see below. What, exactly, am I supposed to uninstall?
I went to my old and trusted friend, Google, for advice, and found this article (among others).
The first step is backing up your data. Well, I don’t have any data to back up, so that isn’t an issue at the moment. It likely will be somewhere down the line, but at the moment, I don’t anticipate that to be an issue. That said, if you do have important data that you want to save, make sure that you back it up first!
Next, they tell you to stop the services. I opened Services (hit the Windows key and type “Services”) and look for any SQL-related services. I shut down MSSQLSERVER, SSAS, SSIS, and so on — basically, anything that looked like it was tied to SQL Server. I checked everything listed under “SQL Server.” I also looked under “Microsoft,” but I didn’t immediately see anything related to SQL Server when I did.
I then followed the steps to uninstall. Step 2 tells you to “search for ‘sql’ in the search box,” but what it doesn’t tell you is that you need to do that from Apps and Features, not from Settings. That step is missing from the instructions. I selected Microsoft SQL Server (Version) (Bit) per step 3 — for me, it was Microsoft SQL Server 2019 (64-bit) –and selected Uninstall. I selected the appropriate prompts, and off it went.
I didn’t think to time how long it took to run, but by my estimate, uninstalling SQL Server took about twenty minutes to run. It appeared to uninstall cleanly; I didn’t see any errors. By the time it was finished, I had about 16GB of new space on my drive.
So, that’s my adventure in uninstalling SQL Server to clear space on my drive. When my new SSD arrives, I’ll make sure it gets reinstalled. (And stay tuned for a future article about installing my new SSD 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.
Looking at this schedule brings up a myriad of thoughts for me.
I don’t ever remember doing three presentations in a single day at any single event in my life. So I’m venturing into uncharted territory here!
Without fail, I absolutely love any SQL Saturday I attend! Also without fail, I am nearly always wiped out at the end of each one. I can only imagine how tired I’m going to be at the end of this one. At least I can sleep on the train ride home!
I purposely scheduled a late train home that night after the event so that I can get a decent dinner down in the City. I figure a couple of drinks during dinner might be in order that night!
My brother, who lives in Queens, has his birthday a few days before the event. I’m hoping to make it a birthday dinner for him that night!
To his credit, Thomas Grohser, who is one of the co-organizers for the event, emailed me asking if I was okay with doing three presentations. I sent him back a two-word reply: “challenge accepted!”
I was very happy to see that, as we requested, Matt Cushing and I have our networking sessions (titled Networking 101 and Networking 102, respectively) scheduled back-to-back! Go check out Matt’s session; it’s a good one!
If there’s any downside to doing three presentations, it’s that I likely won’t be able to attend other presentations that interest me. I do intend to attend Matt’s session (I need to keep my streak going, after all), and I’ll need to check the schedule to see what other sessions I want to attend (if I can).
Of all the SQL Saturdays I’ve ever attended, I’ve attended New York City the most often. For several years, including the first one I ever attended, I only attended NYC SQL Saturday. So for me, being chosen to selected to speak for NYC is special to me.
When I spoke here last year, I had an opportunity to get breakfast at Ellen’s Stardust Diner. It was right next to my hotel and right on my way to the Microsoft office (where SQL Saturday NYC is held). I managed to get there early enough to beat the tourist crowd. This year, I am once again staying in a nearby hotel (only a block away from where I stayed last year). I’m hoping to get there for breakfast again. Yes, I know it’s a tourist trap, but the singing wait staff is something else! You need to check it out at least once!
This past weekend, we (the CASSUG user group) hosted our sixth SQL Saturday. I’ve attended dozens of SQL Saturdays, but the ones that we hold in my own backyard are always the most special to me. This is one of my favorite events of the entire year, and I look forward to it each summer.
I’ll start by talking about my own presentations, which took place in the afternoon (I was scheduled for the last two time slots of the day). My first talk was a lightning talk about business cards. (If you want to know about what I presented, check out my ‘blog article — it pretty much outlines what I talked about.) Mine was one of seven talks, along with talks by Bryan Cafferky, Andy Yun, Deborah Melkin, Michelle Gutzait, Taiob Ali, and Paresh Motiwala. Besides my own talk, I was able to catch the first five talks (unfortunately, I had to leave to prepare for my presentation, so I missed Paresh’s — but that’s okay, because he gives a terrible talk, anyway*), and I can tell you that every one of them was an awesome presentation. I loved every single one of them.
(*ed note: I’m kidding, Paresh! You know I love you!)
All kidding aside… immediately after the lightning talks session, I had my own full-length presentation to do. I debuted a brand-new presentation about ‘blogging. For the most part, it went well, but it isn’t perfect. I did get a couple of comments back saying that they were expecting more about the career aspect of ‘blogging. Apparently, they were looking for a direct link between ‘blogging and career. The idea of my presentation is that ‘blogging can enhance your professional profile and well-being, but apparently, that didn’t come across in my presentation. I’m scheduled to give this talk again in Providence next month, so I’ll have to figure out what tweaks I need to make between now and then.
Other than that, I attended two other sessions: Matt Cushing’s networking presentation, and Thomas Grohser’s interviewing presentation. I’ve attended both presentations before, and they are both great sessions; if you ever have a chance to attend either presentation, I recommended them highly! Tom asked me to attend his; when I attended his previous sessions, he liked my questions and commentary so much that he asked me to come back to ask the same questions and make the same comments — for the benefit of others in attendance. For Matt’s session, it was more a matter of personal pride. He has given the presentation (I think it’s been) six times, and I have been to all six! It’ll be seven for seven next month; he’s coming back to Albany to give his presentation at our user group meeting!
I had to skip out on the second round of sessions to pick up more ice (which was especially critical, since it was the hottest day of the year so far). I didn’t just speak at Albany SQL Saturday; I also served as a volunteer. As I’ve written before, SQL Saturday is an all-volunteer event, and they wouldn’t be possible without all the volunteers who do the behind-the-scenes dirty work, such as setting up, manning the registration tables, making coffee, cleaning up, assembling attendee bags, and all the little things that help make the event go (such as picking up more ice for the coolers). Volunteers are the unsung heroes of SQL Saturday, so if you ever attend an event, make sure that you show them your appreciation!
There were many other aspects of SQL Saturday that made it fun — and are among the many reasons why it is one of my favorite events of the year! I didn’t even mention the speaker’s dinner on Friday night, the after-party on Saturday after it was all over, and the great time I had with many friends whom I often only get to see at these events!
SQL Saturday is a lot of hard work and effort, but it is well worth it! It isn’t just about the data sessions and free training; it’s also about networking, talking to vendors, making friends, and having fun! If you ever get to a SQL Saturday near you, I highly recommend it!
I intend to ‘blog about my experience with my first PASS Summit. Hopefully, my exploits will help others who, like me, are also preparing for the first PASS Summit. This represents the first of those articles.
As I write this, PASS Summit is still four months away. Nevertheless, preparations are in full swing. My flight and AirBnB reservations for Seattle are already set. It’s been a while since I was last in Seattle (I think my last trip was in 2005). Seattle is one of my favorite west coast cities to visit, and I always look forward to trips out to the Pacific Northwest. My only regret about this trip is that baseball season will be over by then, so I won’t be able to catch a Mariners game while I’m there.
I do not intend to rent a car for this trip. To be honest, I’m becoming more and more paranoid about driving a car I don’t own in a metropolitan area with which I’m only vaguely familiar. I did rent a car for SQL Saturday in Washington, and driving around the Beltway was a harrowing experience; during that trip, I became very concerned about returning my rental car with a dent. So for PASS Summit, I intend to rely on public transportation; all my stops — Sea-Tac Airport, my AirBnB, and the Convention Center — are all along the light rail line. If I need a car, I’ll bum a ride off someone, or I’ll contact Uber or Lyft.
Prep work for the event itself on my end is also rolling as well. I’ve gotten emails from PASS about what I need to do to get ready. I’ve registered as a speaker, and I put my presentation into a new PowerPoint template supplied by PASS (and in doing so, I think I made my presentation even better — a lot of the changes will likely end up going into my regular slides). They’re supposed to review my slides, so I’m waiting for them to get back to me as to what changes (if any) I need to make. There are some things about my prep I’m not allowed to discuss — per PASS rules, I’m not allowed to discuss some things until they’ve announced it first — so, alas, I can’t talk about all my prep work.
Last night, I was at Ed Pollack‘s house, helping to prep for this weekend’s SQL Saturday. Knowing that Ed has experience speaking at PASS Summit (he’ll be speaking at his fourth this year), I asked him what I should expect. He told me to “expect at least one question that you can’t answer” during my presentation — maybe something impossible to answer, something I don’t know, or even something that has nothing to do with my presentation. He also told me that PASS Summit would be very busy — apparently there are many activities around PASS Summit that take place. I have friends and family either in or near Seattle; we’ll see how much of a chance I’ll have to get together with them.
I also figure that Matt Cushing‘s advice will likely come into play here. A good chunk of his presentation revolves around activities at PASS Summit. I guess I’ll find out in November how much of it comes into play!
Another thing on my mind is room setups. Although I’ve spoken at many SQL Saturdays, even the largest room in which I’ve spoken pales in comparison to the rooms at PASS Summit. I’m not necessarily nervous about speaking in front of a large crowd — I lost my sense of stage fright a long time ago — as much as I am curious as to how it’s going to work. It’s not something I’ll need to be concerned about until I’m closer to the date, but it is, nevertheless, something that’s on my mind.
I did a Google search for “what to expect at PASS Summit” and came across some interesting links. Some of those links are below (admittedly, I’m listing these for my own reference).
A scary topic and one attack that is apparently more common than I suspected. Before you go further, if you haven’t restored a database backup in the last month, stop and go verify your DR plan works. That’s one of the overconfident issues facing lots of government and businesses. While this might not help your entire organization, at least you’ll have some confidence in your process and that you can recover a database.
This is a great article from Ars Technica and worth reading: A take of two cities: Why ransomware will just get worse. I’d recommend you read it and think about a few things. First, do you have insurance because things (or substitute your own word here) happen? Second, have you really tested a DR plan for some sort of software issue like this? You might think about a way to restore systems in an air-gapped…
For those of you who are not regular readers of my ‘blog, SQL Saturday is a daylong conference centered mostly (but not entirely) around data topics related to SQL Server. It’s also a great networking event, and an opportunity to hook up with a number of data professionals! Check out the schedule to see what sessions interest you!
Additionally, there are three pre-con sessions on Friday, July 19. Unlike SQL Saturday, these sessions are not free, but they provide quality daylong training for specific topics at a decent price. Information about these pre-cons can also be found on the web site!
For more information and to register for the event, visit our website! Upstate New York is a great place to visit during the summertime! Hope to see you there!