Well-designed indexes are an important part of database optimization because they are the key factor in achieving optimal query performance and response time. In the meantime, poorly designed indexes, such as missing or excessive indexes on tables, indexes placed on the wrong column or inadequate index maintenance strategies, can be a source of impaired query and database performance.
Checkout my article here, in which I shared I some guidelines, which you can follow to make indexes more effective, and improve performance during the creation, implementation and maintenance of indexes.
This article is published on SearchSQLServer.techtarget.com.
In many situations, data modification requires several steps. For example, you may need to change the values in two separate tables. You can use transactions to complete these two operations as a unit, or if an error occurs, does not change any of the tables. Another key consideration is that most databases must be compatible with many operations simultaneously. You have several options to configure how data is locked while it is being modified by a user.
Checkout the part-1 of my two part article series on SQL Server Transactions and Locking here, in which you will learn fundamentals about SQL Server transactions, how they work and how to manage them, and how to write procedures that use SQL Server transactions.
This article is published on SQL-SERVER-PERFORMANCE.COM.
The well-designed online analytical processing (OLAP) solution is fundamental to organizations analysis capabilities. That is why, when designing the OLAP solution for your organization, you must ensure that the components of your OLAP solution, including relational data warehouse databases and multidimensional cubes, are designed to meet the business needs of your organization, and provide a solution to users that allows them to locate and analyze the information effectively.
Checkout the part-1 of my two part article series on Designing and Implementing Online Analytical Processing (OLAP) Architecture here, you will learn OLAP database design, options for data warehouse schema design, and key considerations for designing relational data warehouse schema for OLAP applications.
This article is published on SSWUG.org.
With the release of SQL Server 2005 and later releases, Microsoft introduced set of new dynamic management view and function that helps database administrators (DBA) and developers to identify potential index candidates based on query history.
Checkout the part-3 of my three part article series on index-related dynamic management views and function here, in which I discussed these index-related dynamic management views (DMVs), which are useful to identify potential indexes for your queries based representative server activity.
This article is published on SSWUG.org.
The following table lists all builds of SQL Server 2008 known hotfixes, service packs and KB articles that have been released by Microsoft.
Quick Overview:
| Codename | RTM/Service Pack | Build Number |
| Katmai | RTM | 10.00.1600.22 |
| SP1 | 10.00.2531 | |
| SP2 | 10.00.4000 | |
| SP3 | 10.00.5500 |
Microsoft SQL Server 2008 Builds Breakdown:
Note: RTM stands for release to market edition, which is the first supported version of SQL Server 2008, and SP stands for service pack. All SQL Server service packs and hotfixes are cumulative, meaning that each new service pack and hotfixes contains all the fixes that are included with previous service packs, hotfixes and new fixes issues.
Please use comment section, if you find build that is not listed here.
The following table lists all builds of SQL Server 2012 known hotfixes, service packs and KB articles that have been released by Microsoft.
Quick Overview:
| Codename | RTM/Service Pack | Build Number |
| Denali | RTM | 11.00.2100.60 |
| SP1 | 11.00.3000 |
Microsoft SQL Server 2012 Builds Breakdown:
| Build | File version | KB / Description | Release Date |
| 11.00.9000 | 2011.110.9000.5 | Microsoft SQL Server 2012 With Power View For Multidimensional Models Customer Technology Preview (CTP3) | November 27, 2012 |
| 11.00.3350 | 2011.110.3350.0 | 2832017 FIX: You can’t create or open SSIS projects or maintenance plans after you apply Cumulative Update 3 for SQL Server 2012 SP1 | April 17, 2013 *new |
| 11.00.3349 | 2011.110.3349.0 | 2812412 Cumulative update package 3 (CU3) for SQL Server 2012 Service Pack 1 | March 18, 2013 |
| 11.00.3339 | 2011.110.3339.0 | 2790947 Cumulative update package 2 (CU2) for SQL Server 2012 Service Pack 1 | January 25, 2013 |
| 11.00.3335 | 2011.110.3335.0 | 2800050 FIX: Component installation process fails after you install SQL Server 2012 SP1 | January 14, 2013 |
| 11.00.3321 | 2011.110.3321.0 | 2765331 Cumulative update package 1 (CU1) for SQL Server 2012 Service Pack 1 | November 20, 2012 |
| 11.00.3128 | 2011.110.3128.0 | 2793634 Windows Installer starts repeatedly after you install SQL Server 2012 SP1 | January 3, 2013 |
| 11.00.3000 | 2011.110.3000.0 | SQL Server 2012 Service Pack 1 (SP1) | November 6, 2012 |
| 11.00.2845 | 2011.110.2845.0 | SQL Server 2012 Service Pack 1 Customer Technology Preview 4 (CTP4) | September 20, 2012 |
| 11.00.2809 | 2011.110.2809.24 | SQL Server 2012 Service Pack 1 Customer Technology Preview 3 (CTP3) | July 5, 2012 |
| 11.00.2405 | 2011.110.2405.0 | 2823247 Cumulative update package 7 (CU7) for SQL Server 2012 | April 15, 2013 *new |
| 11.00.2401 | 2011.110.2401.0 | 2728897 Cumulative update package 6 (CU6) for SQL Server 2012 | February 18, 2013 |
| 11.00.2395 | 2011.110.2395.0 | 2777772 Cumulative update package 5 (CU5) for SQL Server 2012 | December 18, 2012 |
| 11.00.2383 | 2011.110.2383.0 | 2758687 Cumulative update package 4 (CU4) for SQL Server 2012 | October 18, 2012 |
| 11.00.2376 | 2011.110.2376.0 | Microsoft Security Bulletin MS12-070 | October 9, 2012 |
| 11.00.2332 | 2011.110.2332.0 | 2723749 Cumulative update package 3 (CU3) for SQL Server 2012 | August 29, 2012 |
| 11.00.2325 | 2011.110.2325.0 | 2703275 Cumulative update package 2 (CU2) for SQL Server 2012 | June 18, 2012 |
| 11.00.2316 | 2011.110.2316.0 | 2679368 Cumulative update package 1 (CU1) for SQL Server 2012 | April 12, 2012 |
| 11.00.2218 | 2011.110.2218.0 | Microsoft Security Bulletin MS12-070 | October 9, 2012 |
| 11.00.2214 | 2011.110.2214.0 | 2685308 FIX: SSAS uses only 20 cores in SQL Server 2012 Business Intelligence | April 6, 2012 |
| 11.00.2100 | 2011.110.2100.60 | SQL Server 2012 RTM | March 6, 2012 |
| 11.00.1913 | 2011.110.1913.37 | Microsoft SQL Server 2012 Release Candidate 1 (RC1) | December 16, 2011 |
| 11.00.1750 | 2011.110.1750.32 | Microsoft SQL Server 2012 Release Candidate 0 (RC0) | November 17, 2011 |
| 11.00.1440 | 2010.110.1440.19 | Microsoft SQL Server 2012 (codename Denali) Community Technology Preview 3 (CTP3) | July 11, 2011 |
| 11.00.1103 | 2010.110.1103.9 | Microsoft SQL Server 2012 (codename Denali) Community Technology Preview 1 (CTP1) | November 8, 2010 |
Note: RTM stands for release to market edition, which is the first supported version of SQL Server 2012 R2, and SP stands for service pack. All SQL Server service packs and hotfixes are cumulative, meaning that each new service pack and hotfixes contains all the fixes that are included with previous service packs, hotfixes and new fixes issues.
Please use comment section, if you find build that is not listed here.
The following table lists all builds of SQL Server 2008 R2 known hotfixes, service packs and KB articles that have been released by Microsoft.
Quick Overview:
| Codename | RTM/Service Pack | Build Number |
| Kilimanjaro | RTM | 10.50.1600.1 |
| SP1 | 10.50.2500 | |
| SP2 | 10.50.4000 |
Microsoft SQL Server 2008 R2 Builds Breakdown:
Note: RTM stands for release to market edition, which is the first supported version of SQL Server 2008 R2, and SP stands for service pack. All SQL Server service packs and hotfixes are cumulative, meaning that each new service pack and hotfixes contains all the fixes that are included with previous service packs, hotfixes and new fixes issues.
Please use comment section, if you find build that is not listed here.








