Database user and programming tips
Once you enable your database to be encrypted with Transparent Data Encryption (TDE), the physical database files, and the database backups are encrypted. If your database and database backup are encrypted, then how can you send the encrypted backup to a person outside your organization?
When using Transparent Data Encryption, you might wonder “What is the state of my transparent data encrypted database?” Read on to learn the many different states that a transparent data encrypted database might go through.
By default, SQL Server does not encrypt data in a SQL Server database in an encrypted format. When SQL Server 2008 was introduced, Microsoft implemented Transparent Data Encryption (TDE). When TDE is enabled on a database SQL Server will encrypt the database as data is written to the disk. Read on to learn more...
If you have a database backup of a Transparent Data Encryption (TDE) enabled database, the database backup will contain encrypted data. Because the database backup contains encrypted data you can’t just restore it to any instance. You can only restore the database backup to an instance that contains the same certificate used to originally encrypt the database.
As a DBA your #1 responsibility is to make sure that each of your SQL Server databases are backed up. This tip provides a couple of TSQL scripts that will identify the last backup of each database.
When you install a SQL Server instance you have the opportunity to identify the default location for your instance database backups. Overtime you might decide you want to change the default location for database backups. This tip shows you two different ways to change the default location for your database backups.
Not having instant file initialization turned on slows down the process of adding pages to your database, because prior to allocating the data pages to your database, SQL Server needs to zero out the newly allocated pages. Read on to learn more...
There may be times when you need to perform maintenance against a database that requires you to keep normal database users from connecting to your database while the maintenance is being performed. You want to stop users from connecting right away, but you want the database to be in a state that you can perform maintenance. Read on to learn how.
Have you ever wanted to know how many pages in your database have changed since the last full backup? If so, then you will be glad to hear that the SQL Server 2017 version of the DMV, sys.dm_db_file_spavce_usage, has a new column named modified_extent_page_count, which shows the number of pages that have changed since the last full backup.
Learn how to fix the “cache is out of date” error message when SQL Server Management Studio starts up.
Are you purging the old database mail items stored in msdb? In this tip, Greg Larsen shows you how to purge database mail.
Have you ever wondered how much database mail you have sent in the past day or week? What about those database mail items that were not successfully sent. In this tip, Greg Larsen shows you how to review the database mail items that have been processed by SQL Server.
Greg Larsen shows you how to use the Transaction ID value to identify the object_id for a deleted table.
The transaction log backup is stored in SQL Server proprietary format, just like the transaction log itself. Even though the transaction log backup is in a special format, Microsoft has provided us with the fn_dump_dblog() function to read transaction log backups. This function is undocumented, so you should use care when using this function in a production environment.
Have you ever wanted to be able to see the actual transactions that are contained in the transaction log file? Greg Larsen shows you how to browse the transaction log using an undocumented function.
Database User and Programming Tips Archives