
Applies to
Summary
This article explains the user’s minimal SQL Server and database permissions needed to work with a database using ApexSQL Source Control. Also, the article covers how to grant needed permissions to the user.
This article explains the user’s minimal SQL Server and database permissions needed to work with a database using ApexSQL Source Control. Also, the article covers how to grant needed permissions to the user.
This article provides an in-depth dive into the process of adding multiple SQL Server instances in a targeted folder.
ApexSQL Audit 2020.03 and higher
This article describes how to configure sensitive data classification and auditing in ApexSQL Audit
ApexSQL Doc for MySQL, ApexSQL Doc
This article will explain what documentation settings can be saved as a template in a profile file to reuse it for later projects with the SQL/MySQL database documentation tools. The steps are the same for ApexSQL Doc for MySQL and ApexSQL Doc. For demonstrative purposes, ApexSQL Doc for MySQL will be used.
Applies to
Summary
Managing SQL Server instances often requires various angles of approach depending on the nature of the given tasks. From performing server and database maintenance to health checks, there are several procedures a DBA must implement in order to perform their tasks. While certain tasks can be streamed together, some require a totally different set of tools to be completed in order to improve database security, for example database masking. Masking SQL Server data improves overall security of the SQL Server environment by hiding sensitive data.
Description
This article serves as a guide on how to use ApexSQL Mask from ApexSQL Manage to mask sensitive data.
In order to use ApexSQL Mask from ApexSQL Manage, a SQL Server instance must be discovered and added in ApexSQL Manage, detailed information on the discovering and adding SQL Servers process can be found in the article How to discover SQL Server instances, SSRS, SSAS and SSIS services across the network.
Once this process is completed and ApexSQL Manage is connected to the desired instances, go to the Tools tab in the main ribbon menu.
Check the desired instance from the shown grid that contains a database with sensitive data and click the Mask button. This will run ApexSQL Mask with the dialogue to establish connection to appropriate instance.
The instance that ApexSQL Mask connection dialogue will pick automatically is the one that was checked in ApexSQL Manage. From here, simply select a database that contains sensitive data and click on the Connect button in order to continue with the masking configuration. For this example, AdventureWorksDW database will be used:
While ApexSQL Mask is connecting to the desired SQL Server instance and database, the tool will automatically scan the database for sensitive data and show columns that contain the said data. To toggle between different views, All columns or Classified buttons from the Display group can be used to show all the columns in the database or just the columns that have been auto-detected as sensitive:
If ApexSQL Mask is not installed on the local machine, where ApexSQL Manage is running, clicking on the Mask button will result in prompted message saying that ApexSQL Mask is not installed and will offer to download the tool and install it:
When ApexSQL Mask is successfully installed, clicking the Mask button again will result in actions described above.
Detailed information on ApexSQL Mask and the tool’s features related to this topic are:
Applies to:
Summary
This article describes the ways of exporting various data created within the SQL manage instance tool into a DOCX, PDF, or XLSX file formats.
Applies to:
Summary
DBAs are typically cautious of what they allow to run on their production environment. It goes without saying that this is the best practice that enforces tighter security. After all, it is the DBA’s responsibility that the database or SQL Server instance is not compromised nor its efficiency reduced.
Applies to:
ApexSQL DevOps toolkit – Azure DevOps plugin
Summary
Standard usage of Azure DevOps pipelines implies that projects are built with the build pipelines, where deploy artifacts would be created, and deployed through the release pipelines. This concept is supported with the ApexSQL DevOps toolkit extension for Azure DevOps when it comes to SQL database projects and this article will explain necessary configuration within ApexSQL integrated tasks to setup this workflow.
Applies to:
Summary
This article provides an in-depth look into the automations process of the SQL manage instance tool features.
In this article, all needed database user permissions for linking Amazon Relational Database Service (Amazon RDS) to a source control repository and working with it in the database source control using ApexSQL Source Control will be explained.
When working with Amazon RDS be sure to use the endpoint name of the server that contains amazonaws.com in its name for the connection in SQL Server Management Studio.
© Quest Software Inc. ALL RIGHTS RESERVED. | GDPR | Terms of Use | Privacy