SQL Server management, tutorials, scripts, coding, programming and tips for database administrators
The key challenge for application developers is to build a foolproof system to ensure data security. This is not only more intense, but more complex these days, as many organizations are planning to move their applications to the cloud. Read on to learn more.
One of the most important design decisions that must be made when planning deployment of Azure Cosmos DB involves logical partitioning of data that will populate target collections, graphs, or tables. Selecting the optimal partitioning model has both performance and pricing implications. In this article, we will explore the rationale behind these implications and review the partitioning options.
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.
Anoop Kumar shows you the SQL Commands (T-SQL) to secure PII/PHI data using the SQL Server Dynamic Data Masking (DDM) feature and explores DDM's built in functions to mask all critical data elements. DDM restricts unauthorized users from accessing critical data with no changes in the application.
The majority of traditional database management systems are responsible for making sure that any changes to their data are consistently reflected in the results of subsequent queries. Azure Cosmos DB extends the range of consistency options by providing support for bounded-staleness, session, and consistent prefix models.
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.
This step by step approach explains how to assess your SQL Server migration using DMA. Learn how to understand the behavior of your existing version and what changes need to be made to migrate to a newer version of SQL Server.
In previous articles, we’ve described the main characteristics of two new features known as Virtual Network service endpoints and Azure SQL Database virtual network rules. In this article, we focus on the details of implementing this functionality.
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.
You can use the Data Migration Assistant (DMA) tool to migrate your SQL Server instance to an on-premise SQL Server 2017 or to Azure SQL Database. DMA analyzes data migration issues and provides recommendations to resolve them. Read on learn about the features of DMA and how DMA eases your SQL Server instance migration as well as reduces overall risks, allowing you to complete the migration successfully.
One of the most commonly requested Azure SQL Database features has been support for more granular control of server-level firewall settings. A recently announced public preview of Azure SQL Database and Data Warehouse VNET service endpoints and rules promises to address this limitation.
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.
MS SQL Archives