Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/444384.cloudwaysapps.com/zdhgyehamn/public_html/wp-includes/functions.php on line 6121
Scanning SQL Databases - Quasar Scan
Free downloadPurchase

Quasar Scan user guide

Scanning SQL Databases

< Guide Menu
Table of Contents

This section contains guidelines and best practices for using the SQL Database scanning component of Quasar.

Note: The contents of your SQL DB must be plaintext in order to perform a successful Quasar scan. Databases with encrypted contents or application-specific encodings will not be accessible for scanning by the default scanner, and will require application support & setup at deployment time to be successful.

We recommend a two-stage approach for SQL scanning.

  1. Pre-scanning: Ensure the connection is valid, and identify the tables.
  2. Wide / Deep Scan: Ensure all the tables are covered, determine the scan performance, then complete a deep scan based on your needs.
Auto-Discover Results