Applies to: SQL Server (all supported versions) Azure SQL Database The Transact-SQL programming language provides DBCC statements that act as Database Console Commands for SQL Server. Database Console Command statements are grouped into the following categories. DBCC commands take input parameters and return values.
What is pindbcc PINTABLE in SQL Server?
DBCC PINTABLE does not cause the table to be read into memory. As the pages from the table are read into the buffer cache by normal Transact-SQL statements, they are marked as pinned pages. SQL Server does not flush pinned pages when it needs space to read in a new page.
What is the use of DBCC PINTABLE?
DBCC PINTABLE is best used to keep small, frequently referenced tables in memory. The pages for the small table are read into memory one time, then all future references to their data do not require a disk read. Caution Although DBCC PINTABLE can provide performance improvements, it must be used with care.
Which DBCC commands can accept Unicode and DBCS literals?
All DBCC command parameters can accept both Unicode and DBCS literals. The following DBCC commands operate on an internal read-only database snapshot that the Database Engine creates. This prevents blocking and concurrency problems when these commands are executed.
What is DBCC memorystatus in SQL Server?
The DBCC MEMORYSTATUS command provides a snapshot of the current memory status of SQL Server. You can use the output from this command to troubleshoot memory consumption issues in SQL Server or to troubleshoot specific out-of-memory errors.
What is data_purity in SQL Server 2005?
In SQL Server 2005, a new option, DATA_PURITY, has been added to the DBCC CHECKDB and DBCC CHECKTABLE commands. When you execute a DBCC CHECKDB or DBCC CHECKTABLE command with this option enabled, the command will perform “data purity” validations on every column value in all rows of the table or tables in the database.
How to run the DBCC checkdb command on a user database?
If you have to run the DBCC CHECKDB command with the REPAIR_ALLOW_DATA_LOSS option on a user database or distribution database: Quiesce the system: Stop activity on the database and at all other databases in the replication topology, and then try to synchronize all nodes. Execute DBCC CHECKDB.
