Changes for page sql-tde

Last modified by Nikhil Singh on 2026/07/03 08:32

From version < 7.1 >

edited by Nikhil Singh
on 2025/02/28 11:30

To version < 12.1

edited by Nikhil Singh
on 2026/07/03 08:32

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 1 added, 0 removed)
- image-20250305152543-1.png

Details

Page properties

Content

@@ -1,363 +1,305 @@
--= TDE(backup from smss to azure) =
++= **1. Steps for Implementing Transparent Data Encryption (TDE) FROM SQL Server** =
--1 Create master key in master database (set master key)
++This document outlines the process of **encrypting SQL Server databases** using **Transparent Data Encryption (TDE)** and backing them up to **Azure Storage**. TDE ensures data at rest is encrypted, leveraging a **Master Key (MK)**, **TDE Certificate**, and **Database Encryption Key (DEK)** for encryption.
--2 Create TDE certificate (encrypted by MK)
++The process also includes creating a **credential** for secure backup to **Azure Blob Storage**, providing a scalable and secure solution for storing encrypted databases in the cloud.
--3 Backup the Certificate and private key, By encryption with a password ( did not do it in this case due to storage blog problems)
--4 Choose DB to create the DEK ,Create database encryption key (DEK) with algorithm ( AES= 256) and encryption by certificate
++[[image:image-20250305152543-1.png]]
--5 Set encryption on for the database
---- 6 Create a new credential with the SAS token
--CREATE CREDENTIAL [https://zagpebslab.blob.core.windows.net/sql-backups]
--WITH IDENTITY = 'SHARED ACCESS SIGNATURE',
--SECRET = 'sp=racwdli&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=kBFwlj5S5eqBEE32LM1EFebBY0W94uEFiwOXo3R0yt4%3D';
--Go--
++**~1. Create a Master Key in the master Database**
++The first step is to create a **Master Key** in the master database. This key will be used to encrypt other cryptographic objects, such as certificates and symmetric keys, within SQL Server.
----7 --
--{{code language="sql"}}
--Perform the database backup with the provided parameters
--EXECUTE dba.dbo.DatabaseBackup
--    @Databases = 'dba',                           Replace with your database name
--    @URL = 'https://zagpebslab.blob.core.windows.net/sql-backups',   Azure Blob Storage URL
--    @BackupType = 'Full',                         Full backup
--    @CopyOnly = 'Y',                              Copy-only backup to avoid breaking backup chain
--    @Compress = 'Y',                              Compress the backup
--    @Verify = 'N';                                No verification of backup
--GO
--{{/code}}
++**2. Create a TDE Certificate (Encrypted by the Master Key)**
++Next, generate a **TDE certificate** that will be used to encrypt the **Database Encryption Key (DEK)**. This certificate is encrypted by the **Master Key** created in step 1, providing an additional layer of security.
--The backup was unable to be done from smss to azure ( the MI does not support encrypted DBs to be backed up from smss to azure)
--We have unencrypted a database and backed it up from ssms to azure blob successfully
++**3. Choose the Database to Create the Database Encryption Key (DEK)**
++For the selected database, create the **Database Encryption Key (DEK)**. The DEK will be encrypted by the **TDE certificate** and will use the **AES-256 encryption algorithm** to ensure data is securely encrypted at rest.
--Conclusion: Can be done with and unencrypted DB but not with an Encrypted one>
++**4. Enable Encryption for the Database**
++Once the **DEK** has been created, enable **TDE** for the database. This ensures that all data written to the database is automatically encrypted at rest, providing full protection for sensitive information.
++**5. Create a Credential with a SAS Token**
++Finally, create a **credential** that allows SQL Server to access Azure Blob Storage. This credential is created using a **Shared Access Signature (SAS) token**, which ensures secure and authenticated access to the storage account for backup purposes.
++{{code language="sql"}}
++drop credential [https://zagpebslab.blob.core.windows.net/sql-backups]
++CREATE CREDENTIAL [https://zagpebslab.blob.core.windows.net/sql-backups]
++WITH IDENTITY='SHARED ACCESS SIGNATURE'
++, SECRET = 'sp=racwdli&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=kBFwlj5S5eqBEE32LM1EFebBY0W94uEFiwOXo3R0yt4%3D'
++GO
++
++{{/code}}
--= **Using TDE directly from azure portal** =
++**~ 6. Use a Stored Procedure to Back Up to Azure Storage Account**
++{{code language="sql"}}
++EXECUTE dba.dbo.DatabaseBackup
++@Databases = 'dba',
++@URL = 'https://zagpebslab.blob.core.windows.net/sql-backups',
++@BackupType = 'Full',
++@CopyOnly = 'Y',
++@Compress = 'Y',
++@Verify = 'N'
++{{/code}}
--===== 1 Go to azure key vault ( DemoTestRudi) to generate a key =====
++===  ===
++=== Conclusion: Backup to Azure Storage Account with TDE Encrypted Databases ===
--- Go to keys and click generate
++The attempt to back up an **encrypted database** (with Transparent Data Encryption - TDE) from **SQL Server Management Studio (SSMS)** to an Azure Storage Account was unsuccessful. This issue arises because **Azure does not permit TDE-encrypted databases to be backed up directly to Azure Storage using SSMS**.
--- Name your key (mysqlmikey)
++However, after decrypting the database, we were able to successfully back it up to the Azure Storage Account via SSMS. This confirms that **backups can be performed on an unencrypted database**, but **not on an encrypted database**.
--- Choose a key type (RSA)
---Choose RSA key size (2048-bit)
--Note:
--* switching from 2048-bit RSA to 4096-bit RSA for TDE will affect performance, but the actual impact might be minor, especially on modern hardware and typical workloads.
--* **It will likely affect CPU usage** more than disk I/O, and the impact might be more noticeable during key management operations (key generation, encryption, etc.).
--* If your database is not under heavy load and your hardware can handle the extra processing, the trade-off for better security may be worth it.
--- Click create
++= **2. Enabling Transparent Data Encryption (TDE) Using Azure Key Vault** =
--[[image:image-20250228120622-1.png||height="236" width="542"]]
++**Introduction:** This document outlines the process of enabling **Transparent Data Encryption (TDE)** on an **Azure SQL Managed Instance (SQL MI)** using a **Customer-Managed Key (CMK)** stored in **Azure Key Vault**. The encryption is managed using an asymmetric key from **Azure Key Vault**, ensuring that all data within the SQL Managed Instance is encrypted using a strong encryption algorithm.
--===== 2 Enable TDE  =====
++===== **1. Generate a Key in Azure Key Vault** =====
--- Go to your Managed instance ( sqlmi-ebs-lab)
++**- Navigate to Azure Key Vault:**
--- Click on security and choose Transparent data encryption
++* Go to the **Azure Portal** and select **Key Vault** (DemoRudiTest).
--- Select the type of managed key ( Customer-managed key0
++**- Generate a New Key:**
--- Select the key from the key vault we generated in the key vault( mysqlmikey)
++* Go to the **Keys** section and click **Generate** to create a new key.
--- Make the key the default TDE protector
++**- Configure Key Settings:**
---Click save
++* **Name the Key**: Choose a name for your key, e.g., mysqlmikey.
++* **Key Type**: Select **RSA** as the key type.
++* **RSA Key Size**: Choose an **RSA key size** of **2048-bit**. (optional)
++ Note:
--[[image:image-20250228122106-2.png||height="251" width="511"]]
++* switching from 2048-bit RSA to 4096-bit RSA for TDE will affect performance, but the actual impact might be minor, especially on modern hardware and typical workloads.
++* **It will likely affect CPU usage** more than disk I/O, and the impact might be more noticeable during key management operations (key generation, encryption, etc.).
++* If your database is not under heavy load and your hardware can handle the extra processing, the trade-off for better security may be worth it.
++**- Create the Key:**
--- TDE has now been enabled on the Managed instance
++* Click **Create** to generate the key.
++===== **2. Enable TDE on the SQL Managed Instance** =====
--Conclusion: All the databases have been encrypted by an asymmetric key. The key is the same for each database ( same encryption thumbprint).
++=====  =====
--We are now able to backup databases from SSMS to Azure storage.
++**- Navigate to Your Managed Instance:**
++* Go to your **SQL Managed Instance** (sqlmi-ebs-lab).
++**- Enable Transparent Data Encryption (TDE):**
++* Under **Security**, select **Transparent Data Encryption**.
++**- Configure TDE with a Customer-Managed Key (CMK):**
++* Select **Customer-managed key** as the encryption type.
++* Choose the key you created earlier from **Azure Key Vault** (mysqlmikey).
++**- Set the Key as Default TDE Protector:**
++* Make the key the **default TDE protector** for your instance.
++**- Save Configuration:**
++* Click **Save** to apply the changes.
++=== **Conclusion** ===
++After following these steps, **TDE** has been successfully enabled on your **SQL Managed Instance** using an **asymmetric key** stored in **Azure Key Vault**. All databases within the instance are now encrypted using the same encryption key (identified by the same encryption thumbprint). You can now securely back up these encrypted databases from **SSMS** to **Azure Storage**.
++This process ensures that your data is protected both at rest and during backup, offering enhanced security for your managed databases in the cloud.
--1 CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'YourStrongPasswordHere!';
--GO
--CREATE CERTIFICATE TDE_Certificate
--WITH SUBJECT = 'TDE Certificate';
--GO
--2 USE master;
--GO
++=== **1. Backup Specific Databases Using SQL Server Agent Jobs** ===
--SELECT
--    cert.name AS Certificate_Name,
--    cert.subject AS Certificate_Subject,
--    cert.issuer_name AS Issuer_Name,
--    cert.pvt_key_encryption_type AS Private_Key_Encryption_Type
--FROM
--    sys.certificates cert
--WHERE
--    cert.name LIKE 'TDE%';
++This document describes the process of creating an automated **SQL Server Agent Job** to back up only the **DBA databases** in a SQL Server instance. The backups will occur **daily at 3:00 AM** and will be stored in an **Azure Storage Account** for secure and reliable cloud storage.
++----
--3 BACKUP CERTIFICATE TDE_Certificate
--TO FILE = https://zagpebslab.blob.core.windows.net/sql-backups?sp=racwl&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=eQKxB%2F0bg5cX71PmhUTlGHLCnIwSbe5CLOWVVkaDR1g%3D\TDE_Certificate.cer'
--WITH PRIVATE KEY (
--    FILE = https://zagpebslab.blob.core.windows.net/sql-backups?sp=racwl&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=eQKxB%2F0bg5cX71PmhUTlGHLCnIwSbe5CLOWVVkaDR1g%3D\TDE_PrivateKey.pvk',
--    ENCRYPTION BY PASSWORD = 'AnotherStrongPasswordHere!'
--);
--GO
++==== **1. Create the Backup Script** ====
--USE Normal;
--GO
++====== **- Declaring Variables** ======
---- 6. Create a Database Encryption Key (DEK) and encrypt it with the TDE certificate
--CREATE DATABASE ENCRYPTION KEY
--WITH ALGORITHM = AES_256
--ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
--GO--
++{{code language="sql"}}
++DECLARE @DatabaseName NVARCHAR(128)
++DECLARE @BackupContainerURL NVARCHAR(512)
++{{/code}}
--USE [dba]
--GO
++DECLARE @DatabaseName NVARCHAR(128) DECLARE @BackupContainerURL NVARCHAR(512)
--CREATE DATABASE ENCRYPTION KEY
--WITH ALGORITHM = AES_256
--ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
--GO
++* **@DatabaseName**: A variable to hold the name of the database during each iteration of the loop.
++* **@BackupContainerURL**: A variable to store the URL of the Azure Blob Storage container where the database backups will be stored.
++----
--USE [dba1]
--GO
++====== **2. Setting the Azure Blob Storage URL** ======
--CREATE DATABASE ENCRYPTION KEY
--WITH ALGORITHM = AES_256
--ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
--GO
++{{code language="sql"}}
++SET @BackupContainerURL = 'https://<your_storage_account>.blob.core.windows.net/sql-backups/'
++{{/code}}
--USE [dba2]
--GO
++----
--CREATE DATABASE ENCRYPTION KEY
--WITH ALGORITHM = AES_256
--ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
--GO
++====== **3. Declaring the Cursor** ======
--USE [dba3]
--GO
++{{code language="sql"}}
++DECLARE db_cursor CURSOR FOR
++SELECT name
++FROM sys.databases
++WHERE name LIKE 'dba%' -- Only pick databases that start with 'dba'
++{{/code}}
--CREATE DATABASE ENCRYPTION KEY
--WITH ALGORITHM = AES_256
--ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
--GO
++* **Cursor Declaration**:
++** The cursor db_cursor is declared to loop through the list of databases in the sys.databases system view.
++** The **WHERE name LIKE 'dba%'** clause ensures that only databases with names starting with dba will be processed. For example, databases like dbaTest, dbaProd, etc., will be included in the loop.
++** **sys.databases**: A system catalog view that contains information about each database in the SQL Server instance.
--USE [xwiki]
--GO
++----
--CREATE DATABASE ENCRYPTION KEY
--WITH ALGORITHM = AES_256
--ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
--GO
++====== **4. Opening the Cursor** ======
++{{code language="sql"}}
++OPEN db_cursor
++FETCH NEXT FROM db_cursor INTO @DatabaseName
++{{/code}}
---- 7. Enable Transparent Data Encryption (TDE) on the database
--ALTER DATABASE dba
--SET ENCRYPTION ON;
--GO--
++OPEN db_cursor FETCH NEXT FROM db_cursor INTO @DatabaseName
++* **OPEN db_cursor**: This opens the cursor for reading the results.
++* **FETCH NEXT**: The FETCH NEXT statement retrieves the first database name that meets the LIKE 'dba%' condition and stores it in the @DatabaseName variable. This will be used in the next step where the backup procedure is executed.
--select name, database_id, state_desc
--from sys.databases
++----
++====== **5. Looping Through Databases** ======
--SELECT
--    database_id,
--    key_algorithm,
--    key_length,
--    encryption_state_desc
-- encryptor_type
++{{code language="sql"}}
++-- Loop through each database and execute the stored procedure
++WHILE @@FETCH_STATUS = 0
++BEGIN
++    -- Print current database for logging/debugging
++    PRINT 'Backing up database: ' + @DatabaseName
--FROM
--  sys.dm_database_encryption_keys;
++    -- Execute the DatabaseBackup stored procedure for each database
++    EXECUTE dba.dbo.DatabaseBackup
++        @Databases = @DatabaseName,  -- Specify the current database
++        @URL = @BackupContainerURL,  -- Azure Blob Storage URL
++        @BackupType = 'Full',  -- Full backup type
++        @CopyOnly = 'Y',  -- Use copy-only backup (this doesn’t affect the transaction log chain)
++        @Compress = 'Y',  -- Enable compression
++        @Verify = 'N';  -- Skip verification after backup
++{{/code}}
--  Select * from sys.dm_database_encryption_keys
++* **WHILE @@FETCH_STATUS = 0**: The loop will continue as long as the FETCH command successfully retrieves a database name. @@FETCH_STATUS is a system function that returns 0 if the fetch operation is successful.
++* **PRINT**: This line prints the name of the database that is currently being backed up. It helps with logging or debugging purposes, as you can track which database is being processed at any given time.
++* (((
++**EXECUTE dba.dbo.DatabaseBackup**:
--  BACKUP DATABASE [dba2]
--TO URL = '[[https:~~/~~/zagpebslab.blob.core.windows.net/sql-backups?sp=racwl&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=eQKxB%2F0bg5cX71PmhUTlGHLCnIwSbe5CLOWVVkaDR1g%3D'>>https://zagpebslab.blob.core.windows.net/sql-backups?sp=racwl&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=eQKxB%2F0bg5cX71PmhUTlGHLCnIwSbe5CLOWVVkaDR1g%3D']]
--With copy_only
--GO
++* This calls a stored procedure named dba.dbo.DatabaseBackup for each database.
++* The parameters passed to the stored procedure:
++** **@Databases = @DatabaseName**: Specifies which database to back up (the current database being processed).
++** **@URL = @BackupContainerURL**: Specifies the destination Azure Blob Storage URL.
++** **@BackupType = 'Full'**: Specifies the backup type, which is a **Full** backup (this means all data in the database is backed up).
++** **@CopyOnly = 'Y'**: Specifies that this is a **copy-only backup**. This ensures that the backup does not affect the transaction log chain and does not interfere with regular backups.
++** **@Compress = 'Y'**: Enables compression of the backup, reducing the size of the backup file.
++** **@Verify = 'N'**: Specifies that the backup verification step should be skipped. (Verification can be added if needed for additional safety.)
++)))
++----
--BACKUP DATABASE [dba2]
--TO URL = '[[https:~~/~~/zagpebslab.blob.core.windows.net/sql-backups?sp=racwl&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=eQKxB%2F0bg5cX71PmhUTlGHLCnIwSbe5CLOWVVkaDR1g%3D'>>https://zagpebslab.blob.core.windows.net/sql-backups?sp=racwl&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=eQKxB%2F0bg5cX71PmhUTlGHLCnIwSbe5CLOWVVkaDR1g%3D']],
--\\  COPY_ONLY,  -- Ensures the backup does not affect the regular backup chain
--     COMPRESSION,  -- Optional: Compresses the backup to save storage space
--     STATS = 10  -- Optional: Provides backup progress status
--GO--
++====== **6. Fetch the Next Database** ======
++{{code language="sql"}}
++    -- Fetch the next database in the cursor
++    FETCH NEXT FROM db_cursor INTO @DatabaseName
++{{/code}}
---- Step 1: Drop the existing credential (if needed)
--DROP CREDENTIAL [https://zagpebslab.blob.core.windows.net/sql-backups];
--GO--
++~-~- Fetch the next database in the cursor FETCH NEXT FROM db_cursor INTO @DatabaseName
---- Step 2: Create a new credential with the SAS token
--CREATE CREDENTIAL [https://zagpebslab.blob.core.windows.net/sql-backups]
--WITH IDENTITY = 'SHARED ACCESS SIGNATURE',
--SECRET = 'sp=racwdli&st=2025-02-25T13:28:42Z&se=2026-02-25T21:28:42Z&spr=https&sv=2022-11-02&sr=c&sig=kBFwlj5S5eqBEE32LM1EFebBY0W94uEFiwOXo3R0yt4%3D';
--GO--
++* **FETCH NEXT**: After executing the backup for the current database, this statement retrieves the next database from the cursor and stores it in the @DatabaseName variable. The loop will continue until all matching databases have been processed.
---- Step 3: Perform the database backup with the provided parameters
--EXECUTE dba.dbo.DatabaseBackup
--    @Databases = 'dba',                          -- Replace with your database name
--    @URL = '[[https:~~/~~/zagpebslab.blob.core.windows.net/sql-backups'>>https://zagpebslab.blob.core.windows.net/sql-backups']],  -- Azure Blob Storage URL
--    @BackupType = 'Full',                        -- Full backup
--    @CopyOnly = 'Y',                             -- Copy-only backup to avoid breaking backup chain
--    @Compress = 'Y',                             -- Compress the backup
--    @Verify = 'N';                               -- No verification of backup
--GO--
++----
++====== **7. Closing and Deallocating the Cursor** ======
++{{code language="sql"}}
++-- Close and deallocate the cursor to clean up resources
++CLOSE db_cursor
++DEALLOCATE db_cursor
++
++{{/code}}
++* **CLOSE db_cursor**: This closes the cursor once the loop finishes processing all databases.
++* **DEALLOCATE db_cursor**: This deallocates the cursor, freeing up any resources used by the cursor. It’s a good practice to always deallocate cursors to avoid resource leaks.
--select name, database_id, state_desc
--from sys.databases
++======  ======
++====== **8. Full Script** ======
--SELECT
--    database_id,
--    key_algorithm,
--    key_length,
--    encryption_state_desc
-- encryptor_type
--FROM
-- select * from  sys.dm_database_encryption_keys;
++{{code language="sql"}}
++DECLARE @DatabaseName NVARCHAR(128)
++DECLARE @BackupContainerURL NVARCHAR(512)
++SET @BackupContainerURL = 'https://zagpebslab.blob.core.windows.net/sql-backups'
-- select name, is_encrypted from sys.databases
++DECLARE db_cursor CURSOR FOR
++SELECT name
++FROM sys.databases
++WHERE name LIKE 'dba%'
++OPEN db_cursor
++FETCH NEXT FROM db_cursor INTO @DatabaseName
-- SELECT
--    cert.name AS Certificate_Name,
--    cert.subject AS Certificate_Subject,
--    cert.issuer_name AS Issuer_Name,
--    cert.pvt_key_encryption_type AS Private_Key_Encryption_Type
--FROM
--    sys.certificates cert
--WHERE
--    cert.name LIKE 'TDE%';
++WHILE @@FETCH_STATUS = 0
++BEGIN
-- ALTER DATABASE dba1
--SET ENCRYPTION off;
--GO
++PRINT 'Backing up database: ' + @DatabaseName
++EXECUTE dba.dbo.DatabaseBackup
++        @Databases = @DatabaseName,
++        @URL = @BackupContainerURL,
++        @BackupType = 'Full',
++        @CopyOnly = 'Y',
++        @Compress = 'Y',
++        @Verify = 'N';
--Use dba1;
--DROP DATABASE ENCRYPTION KEY;
++FETCH NEXT FROM db_cursor INTO @DatabaseName
++END
++CLOSE db_cursor
++DEALLOCATE db_cursor
--USE [dba1]
--GO
--
--CREATE DATABASE ENCRYPTION KEY
--WITH ALGORITHM = AES_256
--ENCRYPTION BY SERVER CERTIFICATE TDE_Certificate;
--GO
--
--
--
--ALTER DATABASE dba1
--SET ENCRYPTION ON
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--{{code language="sql"}}
--USE master;
--GO
--CREATE MASTER KEY ENCRYPTION BY PASSWORD = '******';
--GO
--
--CREATE CERTIFICATE EBSphere_TDE_SQL2019_Cert WITH SUBJECT = 'Database_Encryption';
--GO
--
--BACKUP CERTIFICATE EBSphere_TDE_SQL2019_Cert TO FILE = 'D:\temp\EBSphere_TDE_SQL2019_Cert'
--WITH PRIVATE KEY (file = 'D:\temp\EBSphere_TDE_SQL2019_Cert_Key.pvk',
--ENCRYPTION BY PASSWORD='*****')
--
--USE Everest_TDE_Master;
--GO
--CREATE DATABASE ENCRYPTION KEY
--WITH ALGORITHM = AES_256
--ENCRYPTION BY SERVER CERTIFICATE EBSphere_TDE_SQL2019_Cert;
--GO
--ALTER DATABASE Everest_TDE_Master
--SET ENCRYPTION ON;
--GO
--
--USE Everest_TDE_Master_Documents;
--GO
--CREATE DATABASE ENCRYPTION KEY
--WITH ALGORITHM = AES_256
--ENCRYPTION BY SERVER CERTIFICATE EBSphere_TDE_SQL2019_Cert;
--GO
--ALTER DATABASE Everest_TDE_Master_Documents
--SET ENCRYPTION ON;
--GO
  {{/code}}
++===  ===
@@ -367,40 +367,9 @@
--{{code language="sql"}}
--USE master;
--GO
--CREATE MASTER KEY ENCRYPTION BY PASSWORD = '******';
--GO
--CREATE CERTIFICATE EBSphere_TDE_SQL2019_Cert WITH SUBJECT = 'Database_Encryption';
--GO
--BACKUP CERTIFICATE EBSphere_TDE_SQL2019_Cert TO FILE = 'D:\temp\EBSphere_TDE_SQL2019_Cert'
--WITH PRIVATE KEY (file = 'D:\temp\EBSphere_TDE_SQL2019_Cert_Key.pvk',
--ENCRYPTION BY PASSWORD='*****')
--USE Everest_TDE_Master;
--GO
--CREATE DATABASE ENCRYPTION KEY
--WITH ALGORITHM = AES_256
--ENCRYPTION BY SERVER CERTIFICATE EBSphere_TDE_SQL2019_Cert;
--GO
--ALTER DATABASE Everest_TDE_Master
--SET ENCRYPTION ON;
--GO
--USE Everest_TDE_Master_Documents;
--GO
--CREATE DATABASE ENCRYPTION KEY
--WITH ALGORITHM = AES_256
--ENCRYPTION BY SERVER CERTIFICATE EBSphere_TDE_SQL2019_Cert;
--GO
--ALTER DATABASE Everest_TDE_Master_Documents
--SET ENCRYPTION ON;
--GO
--{{/code}}
--
--

image-20250305152543-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.rudim

Size

...	...	@@ -1,0 +1,1 @@
	1	+19.6 KB

Content

Applications

More applications

Need help?

If you need help with XWiki you can contact:

XWiki 14.10.21

Changes for page sql-tde

Summary

Details

Applications

Navigation

Need help?