Author: way0utwest

  • Flipping Sides in SQL Operations Studio

    I’ve been starting to use SQL Operations Studio (SOS) a bit more. This is a small, lightweight editor that is based on Visual Studio Code. It’s fairly limited, though it’s still in preview. You can download it and give it a try.

    One of the things that I like is a consistent UI when writing code. I often hide the OE in SSMS, but I don’t want code moving left and right when I’m working with it. That can be a little jarring.

    When working in SOS, I usually start with a query, and no blades (panes?) open. My workspace looks like this.

    2018-07-09 20_02_47-● SQLQuery1 - SQL Operations Studio

    If I need to commit to version control, I’ll click that button, but then my code moves. (I’m really not committing this query. It’s just an example.

    2018-07-09 20_04_12-SQLQuery1.sql - SQL Operations Studio

    The process is just a little distracting to me, especially if I make the pane wider to more easily see the Object Explorer or file list. I didn’t like this in Visual Studio Code when writing PoSh or Python, and I don’t like it here.

    Switching Sides

    Someone on Twitter posted a couple neat tricks, one of which was moving the panes to the right side. I know some panes in SOS, like the connection one, are always over there, but you can move the main panes.

    I’m surprised I didn’t see it, but I really never even thought about this being an option. I was just annoyed.  If I’d looked in the View menu, I’d see “Move side bar right”. If I do that, I get this.

    2018-07-09 20_10_49-SQLQuery1.sql - SQL Operations Studio

    I could also fine this in the command palette

    2018-07-09 20_11_25-SQLQuery1.sql - SQL Operations StudioThe other cool trick doesn’t do much in SOS yet, but it works in Visual Studio Code. I’ll show it there.

    If I create a new file, VSCode doesn’t know what I’m doing. About half the time I’m writing Python, but I don’t get any of the intellisense or other features unless I save the file and give it a type.

    The other option, is to click the language name in the lower right corner. In the image, I’ve clicked the “PowerShell” and this opens a list of languages. Type “py” and get Python.

    2018-07-09 20_13_17-Untitled-1 - Visual Studio Code

    Cool tricks. I expect that over time SOS will have more than just the “mssql” is has now. I’d expect MySQL, PL/SQL, and more.

    .

  • A few fun pics from vacation

    A few nice pics from vacation. Posting here as I’ll link from an editorial.

    IMG_20180727_132656

    IMG_20180730_174346

    IMG_20180731_140618

    IMG_20180730_195100

    IMG_20180802_115314

    IMG_20180724_202448

  • The Ideal IDE

    When I started working with SQL Server, I spent a lot of time in Query Analyzer and isql.exe. Those were my two main tools, using those to query a database instance in a lightweight manner. At some point Microsoft released Enterprise Manager, which was more useful for some tasks, but overall, I preferred Query Analyzer. Eventually that died away, and we got stuck with Management Studio, which most of us now use. Along the way, I also used DBArtisan, RapidSQL, and a few other IDEs for writing code against a SQL Server.

    These days we have a few choices for doing development and administration on the Microsoft data platform. There is still SSMS, but Visual Studio has gotten quite a few upgrades and extensions to allow work with everything from a local SQL Server to a cloud database to data lakes and more. Microsoft built a lightweight IDE in Visual Studio Code, and released a SQL Server extension for that tool. In the last year, we also saw a preview release of SQL Operations Studio (SOS) from Microsoft, and perhaps this is the direction that Microsoft is moving in the future. There are also other IDEs, such as DataGrip, that some people are using.

    I’m still stuck in the the SSMS mode. Even when I use Visual Studio for SQL Server work, with something like SQL Change Automation, I often switch back to SSMS for lots of my work. I’ve done some work in SOS, but I don’t love the experience overall. Since I have SSMS running most of the time, the speed of SOS isn’t helpful. If I were shutting down and restarting SSMS often, I might feel differently.

    Today I’m curious. I’m sure you all have preferences, but if you could choose only one IDE, what would it be? Let’s imagine that we’re not looking at the current state of the tools, but for whatever functionality you need, whether that’s database development tools, AG management tools, scheduling tools, etc., all of the functionality would be added to VS, VSCode, SSMS, SOS, DataGrip, etc. In that case, what do you prefer?

    I think I’d lean towards keeping SSMS, though I wish it were more open and extensible. Since that’s not likely to happen, I think SOS might be my next choice as an IDE if it has lots of extensions, and I have the ability to enable or disable them for the functionality I need.

    Steve Jones

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 3.7MB) podcast or subscribe to the feed at iTunes and Libsyn.

  • Refreshed and Back from Vacation

    It was a nice break to get away from work for a couple weeks. My family and I traveled 2,000+ miles to Glacier National Park. We camped out each night, and managed to get to both Yellowstone (briefly) and Glacier. Obligatory pic below.

    FB_IMG_1533396327208

    For the most part, I was unwired. There were plenty of places were traveled each day where no connectivity was available. My cell phone was mostly used for pictures, with the “No service” text at the top while in most of the national parks.

    Lots of hiking, and some horseback riding. My wife even managed to get me on a horse one day.

    IMG_20180802_113519

    It was nice to get away, and a little strange to arrive back in a place with more concrete and people than trails and wildlife.

    Going through email and quite a few requests that came in over the last two weeks, as well as starting to prep for SQL Saturday Baton Rouge this weekend. Back in the saddle, as they say, very quickly this week.