Tag: Redgate

  • Monday Monitor Tips: Searching Permission Changes

    During a demo of Redgate Monitor Enterprise to a customer, they asked about how to search for permission changes. This post examines how you can do that in Redgate Monitor.

    This is part of a series of posts on Redgate Monitor. Click to see the other posts.

    Permission Changes

    Redgate Monitor Enterprise adds a few security features to the tool that track things that organizations can struggle to track as their estates grow. There is a security menu item at the top of your Redgate Monitor web page. You can see this expanded on our demo system at monitor.red-gate.com.

    2025-06_0095

    Click the permission entry and you will see this starts on a page that is titled Permissions. There are a few tabs below the title (Permission changes, Servers, Databases, Users). We start on Permission changes, which helps us to see the various changes that have occurred.

    2025-06_0096

    Below this, we see a date box that is set for the last week, along with a few other items. By default we show you the last week’s worth of changes and all the data. However, you can easily alter this.

    2025-06_0097

    This can be a lot of data, especially in an enterprise, so perhaps I only want to see certain things. I can click “Columns and choose which data I care about. Here, I’ll uncheck a few boxes.

    2025-06_0098

    Notice this has rolled up some changes, so I don’t see quite as much as data as I do in the default view. This is useful when I want to see the “who had a change” and not every detail.

    2025-06_0099

    I can, of course, change the date range. We give you some quick defaults, or you can use the calendar picker to choose a range.

    2025-06_0100

    When I do this, I only see some changes, those that apply to that date range.

    2025-06_0101

    If I want to further filter things, I can choose that item. You can see the various items below I can choose from.

    2025-06_0102

    Let’s set  this to “Changed by” the sa account. When I do that, notice the “Filters” icon is annotated saying I have 1 filter condition. I also only see the one row changed by SA.

    2025-06_0104

    I will expand my date range and remove the filter while adding all the columns, and I see this data:

    2025-06_0107

    That’s a lot, but I can change the density. Here are the choices.

    2025-06_0106

    Here is compact. Now all 10 rows fit on the page:

    2025-06_0108

    Comfortable only shows 7 rows (9 in standard).

    2025-06_0109

    Lastly, I can set the number of rows on the page in the lower right.

    2025-06_0110

    Summary

    Security is becoming something more people need to report on, especially public companies or those regulated. This feature of Redgate Monitor helps you satisfy auditor requests with the information they need to verify you are watching your systems.

    Or, at least that you know Redgate Monitor is doing so.

    Redgate Monitor is a world class monitoring solution for your database estate. Download a trial today and see how it can help you manage your estate more efficiently.

  • Monday Monitor Tips: Customizing Data Retention

    One of the biggest challenges with monitoring data is managing the volume over time. Lots of bespoke/home-grown solutions don’t do this well, and some commercial products have a gross approach that might not meet your needs.

    Customers constantly ask me about this, so here’s a quick tip on how you can manage data retention in Redgate Monitor.

    This is part of a series of posts on Redgate Monitor. Click to see the other posts.

    Checking the Configuration

    As with most things in Redgate Monitor, this is a config item. In your Redgate Monitor solution (or on the public demo site), you can find the configuration gear icon in the upper right.

    2025-05_0114

    Click this and you get to the settings page. Scroll down to the Preferences area and there is a Data retention settings link. Click that.

    2025-05_0116

    You will get to the Data retention settings page (public site), which has a few sections at the top. You will be setting this per Base Monitor, using the drop down at the top.

    Scroll below these to the data retention section, which you see at the bottom:

    2025-05_0117

    In this section, you see quite a few different sections. I’m showing the trend data below.

    2025-05_0118

    There are sections for

    • trend data- long term data for understanding how performance and baselines work
    • performance troubleshooting data – query, waits, plan, etc. data

    Each of these sections is described, along with where the data is displayed. You can see that in the image above.

    To the right of these, are the retention settings. I’ve got an image of the first few items. You can see the time for which to retain data and then the current size of that data.

    2025-05_0119

    You can set a fairly granular level of retention for data here, broken out by the various data elements we capture.

    The choices for retention are shown below, including indefinitely (be careful of this one).

    2025-05_0120

    We have this documented, along with what we think are good defaults on this page. For example, we keep top query data for only one week, since this is a lot of data. However, if you want more time, then set it to something that works for you.

    Summary

    Data management is always a challenge, both in production databases and in our monitoring systems. Redgate Monitor gives you lots of choices, and those can vary by Base Monitor, so if you have a BM in the cloud doing some stuff and one on premise doing other things, you can set separate retention settings. That can be handy, especially when the cost of storing things can vary dramatically.

    Watch this over time and adjust settings as needed to keep your system performing optimally.

    Redgate Monitor is a world class monitoring solution for your database estate. Download a trial today and see how it can help you manage your estate more efficiently.

  • The Book of Redgate: Ingeniously Simple

    Redgate has been known for many useful tools that are easy to use. We’ve tried to do that in all our point tools. We talk about simplicity all the time and when we release something that isn’t simple, lots of people question why.

    Perhaps not enough or with enough pushback, but we do talk about simplicity.

    One of the pages in the book was devoted to merely expressing ingeniously simple. It’s written in a number of languages.

    2025-05_0105

    The goal of ingenious simplicity is to build things that people can use without resorting to complex manuals and example code. SQL Compare is a great example of this. Enter a few database connections and click Compare and you get an easy report. There’s a big Deploy button on top to help you sync your databases.

    I think we’ve done a good job of building some simple tools over the years. Perhaps now we’re in a more complex environment, but we are trying to keep things simple and provide clues to help users understand how the tools work.

    I have a copy of the Book of Redgate from 2010. This was a book we produced internally about the company after 10 years in existence. At that time, I’d been there for about 3 years, and it was interesting to learn a some things about the company. This series of posts looks back at the Book of Redgate 15 years later.

  • DevOps Devour Hour Slides

    Here are the slides from my talk today at the Redgate NYC Devour Hour: Architecting Zero Downtime Deployments.pptx

    The Repo is here: https://github.com/way0utwest/ZeroDowntime

    An interesting question on feature toggles: Would you use Extended Properties for a feature toggle flag?

    My answer:

    I wouldn’t. I find Extended Propeties (and triggers) to be hidden inside databases and I don’t like hidden things. They fall through the cracks, it’s hard to remember they exist, and more. Plus Extended properties aren’t easily programmed.

    I would love

    alter table add (or update) extended property

    and a way to query these

    select * from table.properties

    Instead we have a messed up sp_add/update property with a very, very unintuitive set of parameters.