Concurrency Models in SQL Server 2012
The SQL Server Database Engine supports two different concurrency models: pessimistic concurrency and optimistic concurrency. Learn more.
Read More
The SQL Server Database Engine supports two different concurrency models: pessimistic concurrency and optimistic concurrency. Learn more.
Read More
SQL Server supports two methods of data encryption: column-level encryption and transparent data encryption (TDE). Learn more.
Read More
In addition to the potential performance gains for complex views that are frequently referenced in queries, the use of indexed views has several advantages. Learn more.
Read More
Although the SQL Server Database Engine does not have any practical limitations concerning the number of indices, it is advisable to limit them. Learn why.
Read More
Fragmented index data causes the SQL Server Database Engine to perform additional data reads, and decreases performance. To fix this problem, you must rebuild fragmented indexes. Learn more.
Read More
To get information concerning internal index fragmentation in SQL Server, use the DMV sys.dm_db_index_physical_stats. Learn how.
Read More
A nonclustered index in SQL Server has the same index structure as a clustered index, but doesn’t change the physical order of the rows in the table, and the leaf pages consist of an index key plus a bookmark. Learn more.
Read More
A clustered index is built by default for each table for which you define the primary key using the primary key constraint. Learn more.
Read More
SQL Server indices are a separate physical data structure that enables queries to access one or more data rows fast. Proper tuning of indices is key for query performance. Learn why.
Read More
The SQL Server system base tables have the same logical structure as base tables, and you can use the same T-SQL statements to retrieve information from them as used with the base tables. Learn more.
Read More
If you want to generate the compiled form each time a SQL Server procedure is executed, use the WITH RECOMPILE option. Learn more.
Read More
Starting with SQL Server 2005, you can capture and handle exceptions using two statements, TRY and CATCH. Learn what “exception” means and how to use these statements.
Read More