Tag: Redgate

  • Prompt in ADS

    Ever since VS Code and Azure Data Studio came out, people have been asking for SQL Prompt to port over. I’ve been right there with you, though unsure of the value, given how UI dependent Prompt is for users.

    Things have changed.

    sql-prompt_early-access_social-graphic_1200x630

    There’s an EAP program, with an early look at the formatting part of Prompt in ADS.

    I’ve been using this for a few weeks, and it’s different, but it works well. All my styles from SSMS are ported and linked, and it’s a quick set of keystrokes, albeit different ones, to format code.

    I’m curious to see what others think, so join the program if you want formatting in ADS and are willing to give some feedback.

  • Take the 2020 State of Database DevOps survey

    It’s still 2019, but we’re looking forward to 2020 and wonder how your world has changed since our survey last year. There are a number of questions and this will probably take 20 minutes to complete, but you have a couple incentives:

    • Completed surveys donate $1 to UNICEF
    • You could win a 64GB iPod Air

    You can take the survey here: https://www.surveymonkey.co.uk/r/FWCVCBJ

    Feel free to pass this along to your friends as well.

  • Cleaning up the [NOT] NULL for Columns with SQL Prompt 10

    SQL Prompt 10 is out and there are a few interesting things that have changed in the product. One of these is the Quick Fixes, inspired by some other IDEs that help developers learn to fix their code.

    This post looks at one of the most common things developers ignore, and I’m guilt of this in many of my demos and code.

    Defining Columns

    When I create a table, I often will write some code like this:

    CREATE TABLE dbo.EventSchedule
    ( EventScheduleKey INT IDENTITY(1,1)
    , ScheduleName VARCHAR(100)
    , StartTime DATETIME2
    , EndTime DATETIME2
    , Active BIT)
    GO

    This looks fine, and it works. However, it’s a SQL code smell, and it’s something that you should avoid. The problem with this code, is that I haven’t specified the nullability setting for the columns. I am assuming a default for my database, which has worked for me, but as I work with a more diverse set of customers, I know this isn’t a good practice.

    SQL Prompt 10 actually catches this. If I screenshot the code, I can see the green squiggly that notes there’s an issue.

    2019-11-13 15_00_11-SQLQuery3.sql - Plato_SQL2017.sandbox (PLATO_Steve (60))_ - Microsoft SQL Server

    That’s a code analysis item that our software has flagged. If I hover over the area, I see this:

    2019-11-13 15_02_49-SQLQuery3.sql - Plato_SQL2017.sandbox (PLATO_Steve (60))_ - Microsoft SQL Server

    That’s good, but if I’m a junior developer, what do I do? What does this mean? One of the very nice things with SQL Prompt 10 is that we provide some guidance, similar to what Visual Studio does.

    Look on the left of the image below. I’ve put the cursor on the line with the green squiggly. There’s a little yellow light bulb in the margin. This is a note that we provide a fix here. You can click the keyboard or the yellow icon.

    2019-11-13 15_07_30-SQLQuery3.sql - Plato_SQL2017.sandbox (PLATO_Steve (60))_ - Microsoft SQL Server

    When you do this, you will see that there a few choices. I can fix this (the wrench or spanner icon), get the details for this code issue (the eye icon) or see all issues in my code.

    2019-11-13 15_07_42-SQLQuery3.sql - Plato_SQL2017.sandbox (PLATO_Steve (60))_ - Microsoft SQL Server

    If I click the “fix” icon, I’ll see this:

    2019-11-13 15_07_49-SQLQuery3.sql - Plato_SQL2017.sandbox (PLATO_Steve (60))_ - Microsoft SQL Server

    NOT NULL has been added, but the NOT is highlighted. I can hit <enter> and this will stay there, or hit Backspace and remove the NOT. Either way, I get the code cleaned up.

    At least some of it. You see the next green squiggly on the line below.

    SQL Prompt continues to be one of the best productivity tools for developers working with SQL Server. If you have it, look for the quick fixes, and code smell squiggly lines. If you haven’t, download a trial today and see how it will help you become a better T-SQL developer.

  • Data Masker Reads Column Classificiations

    One of the newer features in Data Masker for SQL Server is the ability to read column classifications and suggest rules to clean the data. I decided to give this a try and see how things work.

    Importing Column Classifications

    I created a new Masking Set, and I do like the new connection dialog. It works well makes it easy for me to focus my masking on a schema.

    2019-11-13 10_49_03-Data Masker for SQL Server

    From here, I went to the Tables tab to check on the classifications. I didn’t see any, which felt slightly strange.

    2019-11-13 11_01_39-Data Masker for SQL Server

    I went back to SSMS and double checked my work. I do have things classified.

    2019-11-13 10_47_58-Data Classification - StackOverFlow - Microsoft SQL Server Management Studio

    After a quick reach out to the team, I remembered that a plan is an item you need to create and save. In this case, the feature is importing information from the database. I can then work with it in a plan. To get the data, I click the “Export/Import Plan” button at the bottom of the Tables tab.

    2019-11-13 11_10_57-Data Masker for SQL Server

    This brings me a dialog of the plan details. I can choose to import a plan from a CSV file, or from the SSMS classifications. I’ll choose the latter.

    2019-11-13 11_11_34-Data Masker for SQL Server

    Note: plans are specific to a controller. If I have two controllers, I need to import the plan into both (or all). When I click “Import”, the data is added to my plan. I can see that now there are four columns classified.

    2019-11-13 11_18_37-Data Masker for SQL Server

    If I expand one of these nodes, like the Users table, I see that there are columns marked as sensitive and the comment includes the classification. That’s very handy for deciding how to mask the data.

    2019-11-13 11_23_11-Data Masker for SQL Server

    Another welcome improvement is that I can change my plan sensitivity for all the columns in a table at once. In this case, I’ll right click the Sensitivity column for a table. I can then pick “Check”.

    2019-11-13 11_25_56-

    Once I do this, all columns are set to check for this table.

    2019-11-13 11_26_07-Data Masker for SQL Server

    I can also multi-select columns (with the CTRL key held down) and then right click. In this case, I can pick three and then choose “sensitive”.

    2019-11-13 11_26_53-Data Masker for SQL Server

    They’ll all be set, and I can see that I need to get to work.

    2019-11-13 11_28_35-Data Masker for SQL Server

    Quick Rules

    One other nice thing is that I can create a rule for multiple columns at once. If I have a few selected, I can right click and create a rule. I’ll choose Substitution rule here.

    2019-11-13 11_29_16-

    This brings me up a dialog with the columns already in my rule, and now I can pick the specific customizations I need for each.

    2019-11-13 11_29_24-New Substitution Rule

    It’s a little thing, but it greatly speeds up the process of masking data.

    Give It A Try

    Data Masker is part of SQL Provision, and it’s an amazing tool that allows me to mask data in almost any way I can think of to protect data in non production environments.

    There are some other nice enhancements in this v6.3.13.x release. If you haven’t given Data Masker a try, do so today.