Working with an estate of hundreds of servers? Finding it difficult to keep a shared, central list of server information up to date?
Everyone seems to have their own solution for maintaining the details their team needs for SQL Server Management Studio/Remote Desktop. Maybe you store this information in a spreadsheet or text file on a shared network drive, have a local copy, or use a specialised separate program to coordinate this knowledge. Maybe you even have it printed out and taped to the wall!
All these methods come with their pros and cons, but besides the pricier options, most require regular manual work. We’ve got another way for you to try, and it’s free.
How Aireforge Studio can help
When using Aireforge Studio, you start by setting up all your servers in the Estate module. The list then becomes your central workspace for you to compare settings, run health checks, scripts etc.
To launch SSMS or Remote Desktop, there’s a right-click option, then the relevant address details are pre-populated. No more moving between documents or copy and paste! You can even give servers friendly names to make your workspace faster to navigate.
For teams, there’s an alternative to a centralised document: share a secure, password protected Aireforge profile. That way, you’re only inputting this data once and everyone is always getting the recent information.
Are you taking some time off over the holiday period? Do you have a change freeze scheduled over the next few weeks?
If so, taking a snapshot of your servers’ configuration is a helpful way of making your work less stressful when you return. That way, when you get back after your time off, you can compare the state of your servers post-holiday with how you left them. You wouldn’t leave your house for the break without properly securing it, so why should your servers be any different?
Comparing snapshots is easy in Aireforge Studio. In the application, take a snapshot of your servers this week. Then when you get back, it’s only a few clicks to compare it against the same servers. You get a clear list of the differences between them, so you’ll immediately be able to see any changes anyone has made. No more hidden surprises, and it makes it so much simpler to revert things if you need to.
Watch our video or read the support page to see how. Then, relax and enjoy your time off, knowing you’ll be prepared for your return.
Configuring SQL Server to run at peak performance is a skill that can take years to learn. But when you need to configure and maintain tens, hundreds or even thousands of instances, it’s a task that can overwhelm even the most seasoned DBA.
The Advise module for Aireforge Studio helps to combats this. Advise analyzes your SQL Server instances and provides suggestions for optimization and best practices. Here, we’ll take a look at some of its key features and how it can improve the performance, security and stability of your SQL Server estate.
Advise offers support for all versions of SQL Server, as well as Azure SQL Database and Azure Managed Instances. It combines expert database analysis with a focus on ease of use. At Aireforge, our extensive database management experience underpins Advise’s recommendations. We’ve taken fundamental operational checks, along with best practices from our experience working on mission critical and high-transaction databases, and packaged them into dynamically generated scripts you can run on your own estate. The tool provides a reliable and time-efficient alternative to writing and maintaining your own diagnostic scripts.
Advise supplies over 50 different warnings and suggestions. Let’s take a look at five key areas.
1. Index Management
Poor indexing can severely hit performance. A lack of useful indexes can lead to excessive scanning of indexes, tables and heaps, potentially crippling the I/O subsystem. Inefficient or fragmented indexes will also result in excessive I/O and CPU usage, as fragmented indexes will use a greater number of pages, missing columns will require another table hit / lookup and missing indexes could result in inefficient query plans and / or expensive table scans.
It’s critical to ensure your tables are indexed properly so that data can be quickly accessed. At the other extreme, duplicate indexes or overlapping indexes require more resources to maintain the duplicated data, increasing the amount of processing needed when data is inserted or modified. Duplicate indexes can also result in sub-optimal execution plans as more indexes means more options for the optimizer and a greater risk of timing out before a “good enough” plan is found.
Getting index management right will result in major performance improvements and Advise will suggest changes to speed up your queries and free up resources by removing duplicates and merging overlapping indexes.
Advise detects duplicate indexes, where the same columns are indexed in the same order, giving you the dynamically generated script to drop the duplicate. It also highlights superseded indexes. This is where index A and index B are indexed on identical columns, but B has additional columns. Where A and B have ‘included columns’, Advise may suggest a creating a third index to replace A and B. Data from the missing index statistics are also factored into these checks, suggesting additions to existing indexes where possible or completely new indexes if required.
Advise also detects disabled, unused or hypothetical indexes, that are consuming resources but simply aren’t used. Dropping these kinds of indexes are quick wins that can save huge amounts of storage and again, give the optimizer an easier time.
Screenshot 1: comparing indexes in Aireforge Studio.
Screenshot 2: choosing analysis options in Aireforge Studio.
2. Configure SQL Server’s Automatic Behavior and Settings
Many of the default settings for SQL Server haven’t been updated in years, despite the increased speed of new hardware. Outdated default settings can cause poor performance and operational issues, so Advise looks at the SQL Server settings and suggests adjustments. This includes:
Recommending min/max memory allowance.
Recommended trace flags.
Operating system best practices.
Advise also ensures that non-default settings have not been used that could impact the performance, stability and integrity of a server. Including:
Checking whether auto shrink and auto close are enabled (both of which can cause massive performance issues if misconfigured).
Ensuring auto statistics is enabled to support the optimizer in creating more efficient query plans.
3. Optimize Parallelism Settings
One of the jobs of the SQL Server query optimizer is planning how to run queries on multiple threads. Advise will recommend an optimal parallelism cost threshold. This is the threshold that SQL Server uses to determine when to run a query using multiple threads. A low setting can cause the optimizer to waste time planning multi-threaded queries. A high one can lead to all queries only ever using a single thread. Choosing the optimal cost threshold for parallelism is a delicate balance and Advise helps you tune it correctly.
4. Database File Management
Running out of space when writing to the database file can cause a major service outage. Catching this issue early is critical so Advise warns if a database file is nearly full. Advise will also make best practice suggestions such as an optimum file count per CPU core. It also alerts you if data files in the same group have differing sizes, or if a data file has excessive free space. These checks are applied to all databases, including tempDB.
5. Database Monitoring and Log Analysis
Advise reviews the SQL Server logs to check for possible problems, or opportunities for improvement. This includes alerts if an I/O request takes longer than 15 seconds to complete or if the server is constrained by low memory. These alerts can be the difference between catching performance issues before anyone notices and unplanned downtime that disrupts your entire user base.
Advise Makes Tuning Simple
Advise has many other checks in addition to the ones mentioned above, but common to all of them is that as well as dynamically generated SQL, you’re given human-readable information to understand what the suggested action is, how to take it, and why it’s being shown to you at all. This way, you can not only optimize your database, but have confidence while doing it.
Every check has come from our experience working on real production databases, and we routinely use it in our consulting work in high-performance and high-transaction enterprise solutions. Advise is written by busy DBAs, for busy DBAs. For more information on Aireforge Studio, visit our website.
Working with large numbers of SQL Server and Azure instances can be extremely challenging. If you’re like most DBAs and developers responsible for estate management, you’re already juggling other priorities. Since you may have inherited the databases or accidentally stepped into the role, it’s unlikely you have time to manually monitor, trouble-shoot, configure and update, on top of keeping everyone involved happy!
If you can’t easily monitor and configure all those databases, how can you make sure they’re consistently patched and running at peak performance? How can you discover issues such as out of sync user access rights and configuration options, or even just run SQL queries on multiple databases at once?
These are some of the issues we wanted to solve when we created Aireforge Studio. This application supports busy DBAs and developers in charge of database estates, using the same workflow whether you’re working with ten databases or ten thousand. All the features described below are totally free.
Simple Estate Management
One of the major obstacles for DBAs with large estates is simply keeping track of them. The Estate module keeps all of your database instance knowledge in one place. Adding new instances is straightforward with the Import option, which allows you to import SQL Server instances from existing database lists in SSMS or from CSV files. You can also discover instances using SQL Browser.
When the number of database instances runs to hundreds or thousands, quickly navigating the entire list becomes unwieldy. What you need is a way to collect related databases together. The tag manager allows you to group instances and assign informative names such as production, testing, and staging. You can add multiple tags to give further detail, such as regional tags. Then, when you want to perform an action against an entire group (such as comparing their configurations), you can apply the action to a specific tag. With the click of a few buttons, Aireforge Studio allows you to efficiently manage an entire estate.
Screenshot: Categorizing a server in Aireforge Studio
Aireforge Studio also includes a way to quickly check the health of database instances and provides several Health Check scripts out-of-the-box for highlighting immediate and potential SQL Server issues. You can also add your own Health Checks, tailored to your specific estate, and run them over hundreds of servers at a time.
Screenshot: health check results in Aireforge Studio
The Power of The Script Module
Many teams use SQL Server’s Central Management Servers for running queries across multiple servers. We did too, but we also found it to be lacking a lot of the functionality needed from a scripting tool, like being able to select individual instances with ease or changing how results are displayed. Using the Script module, you can run queries against the estate you’ve already loaded into your profile, targeting existing groups or individual servers.
Screenshot: running a query across multiple servers in Aireforge Studio.
Discovering Configuration Differences
Aireforge Studio’s Compare module (originally called OmniCompare) makes it easy to find differences between SQL Server and Azure instances. This module compares a variety of configuration and metadata, including build version, users, audit, trace flags, databases, jobs – essentially everything except the data itself. This type of analysis is often a key first step in diagnosing performance issues. As the size of your estate increases, it becomes difficult to determine whether configurations are out of sync. For example, if one SQL server is known to be suffering from poor performance, comparing tuneables such as the default autogrow value in SQL server can help you understand whether the database’s file size is a factor.
The Compare module is a great way to build a fingerprint of the database instance for analysis. Take a snapshot of configuration before making changes, and another after them, so you can easily identify anything that happened unexpectedly as a result. If you have a server you’d like to act as a benchmark for the rest of your estate, take a snapshot, Compare, then you’ll have a list of the changes required to standardize your servers.
Screenshot: comparison results in Aireforge Studio.
The Compare module also offers a command-line interface (CLI) for those DBAs who want to drive comparisons from the command line via a comparison file. One of the biggest benefits of the CLI is that you can use it to integrate Aireforge Studio into your deployment pipeline, SQL Server Agent, or other custom scripts.
Aireforge Studio was designed for database management professionals of all levels. It’s easy to use for accidental DBAs, but there are plenty of features to help power users get their work done faster, such as the ability to add custom Comparisons and Health Check scripts. We’ve been working with SQL Server for over 30 years and use Aireforge Studio routinely in our work as consultants in high-performance and high-transaction enterprise solutions.
Adding these scripts to Aireforge Studio allows us to perform complex tasks at scale. To get the job done, you can customize everything from the Comparison scripts you run to the built-in Health Checks you require. We also provide the scripts in plain text so you can understand, copy and adapt them to better suit your estate.
Try Aireforge Studio Today
Aireforge Studio Community Edition (which is totally free) makes it easy for busy DBAs and developers to manage large, high-performance estates. Whether you’re an accidental DBA or an experienced power user, it keeps you in control of your databases.
Do you have scripts you created, or ideas for scripts, that you believe would be useful for other Aireforge Studio users? Please get in touch! We’re always looking to expand the tools available to make SQL Server estate managers’ lives easier.
We’ll keep this short, but we’ve created a scripting tool for running queries against multiple SQL instances via Aireforge Studio. Oh, and it’s FREE.
The Microsoft Central Management Servers (CMS) are great (link), but they’re lacking functionality and haven’t had much attention in recent years. So, given that Aireforge users already have their estates loaded into their profiles, we thought it made sense to build a scripting module into Aireforge Studio. You can use the same servers and groups from the estate manager or select individual servers; giving you more control over which scripts are run and where. You can also export to CSV, validate your queries before running them and change how the results are displayed or grouped.
We have a healthy backlog in JIRA for Script, but any feedback is always appreciated. If you think that we’re missing something, please let us know (via Wantoo) and we’ll do our best to implement it.
We’re pleased to announce that Aireforge Studio is now officially live and supported. Version 1.0.7 ships with hundreds of improvements with a new UI, simpler comparisons with advanced options, 2017 support and our new tuning / best practices module; Advise.
Depending on your version, the application should prompt to update after starting. If not, please download the latest version using the link below.
The new Advise module within Aireforge Studio analyses instances, databases, tables and indexes, before providing recommendations. The growing list of checks vary from best practices and naming convention violations to orphaned users and missing, duplicate or overlapping indexes.
The Compare module within Aireforge Studio performs a growing list of comparisons, which can be restricted if certain values are known to differ, such as core count or edition (e.g. Enterprise vs Developer).
Common use cases for Aireforge Studio Compare are checking production databases against staging and / or staging against test, auditing the SQL Server estate, sharing configurations with colleagues / support teams.