How to Enable, Suspend, and Resume TDE Encryption Scans in SQL Server Always On

 

Transparent Data Encryption (TDE) is a crucial security feature in SQL Server that protects data at rest by encrypting database files. In an Always On availability group, managing TDE encryption scans efficiently is essential to ensure minimal performance impact and seamless data protection. This guide will walk you through the process of enabling, suspending, and resuming TDE encryption scans in SQL Server Always On, helping you maintain security while optimizing system performance. Whether you need to temporarily pause encryption scans for maintenance or resume them after an interruption, these steps will ensure smooth database operations.

For encrypting an SQL Server database, please review Encrypt an Existing MS SQL Server 2019 Database in an Always On Environment Using TDE

How to Decrypt a TDE-Enabled Database in a SQL Server Always On Environment

 

There could be various reasons for removing an existing TDE (Transparent Data Encryption) implementation from SQL Server databases. You may be considering an alternative encryption solution, experiencing performance issues, or needing to share a copy of the database or its backup with other business units that do not support TDE. Regardless of the reason, properly decrypting a TDE-enabled database in a SQL Server Always On environment requires careful execution to ensure data integrity and minimize downtime. In this guide, we will walk through the steps to safely remove TDE encryption from a database while maintaining availability and security.

For encrypting an SQL Server database, please review Encrypt an Existing MS SQL Server 2019 Database in an Always On Environment Using TDE

Configuring a Second Listener on EXACC ASM Cluster to fix Cluster ASM monitoring Issues in Oracle OEM

1. Introducing the Issue

Recently, we encountered an issue in our OEM while trying to monitor the EXACC ASM Cluster. This is my EXACC cluster configuration in OCI.

The OEM displayed the cluster status as down, despite all configurations being correct. The error was as follows: 

"failed to connect: java.sql.sqlrecoverableexception: listener refused the connection with the following error: ora-12514, tns:listener does not currently know of service requested in connect descriptor"

DBSAT Security Series – Part 2: Identifying Sensitive Data Using DBSAT Discover

Introduction

DBSAT Discover is a standalone, Java-based component of the Database Security Assessment Tool that identifies sensitive data within your database. Unlike the Collector and Reporter, Discover works independently and focuses on scanning tables and columns for patterns that match PII, financial, or other confidential information. Building on the foundation covered in Part 1 of this series, EnhancingQuery Performance: Leveraging In-Memory Optimized Dates in Oracle 23ai, where we explored configuring and using the main DBSAT tool, Discover, helps you take the next step by revealing exactly where sensitive data resides, so you can strengthen your overall security posture.

DBSAT Security Series – Part 1: Configuration and Reporting with DBSAT

Oracle Database Security Assessment Tool (DBSAT) is a popular command-line tool that helps identify areas where your database configuration, operation, or implementation introduces risks and recommends changes and controls to mitigate those risks. This tool is essential for database administrators and security professionals who want to ensure their Oracle environments are protected against both internal and external threats.

Configure Nagios to monitor Oracle database on a remote Linux Host Using CHECK_ORACLE_HEALTH

Monitoring Oracle Database with Nagios involves using plugins and configurations that allow Nagios to check the status and performance of the Oracle Database.

JBO-25077 OEM has a problem with collecting the information of a host

 When I opened the target host to view the related report, I got this page.