SQL Server Articles

Terms used in this article Execution or SQL Execution represents a call to a Stored Procedure or an SQL Batch. General Description This process creates a Baseline repository that holds summarized data of all SQL Executions executed on an instance of SQL Server. The repository lights up your SQL Server’s activity and exposes interesting information [...]

Detailed walkthrough on creating a simple application using Visual Studio LightSwitch.

This article demonstrates how to manage database projects with Visual Studio 2010.

This article demonstrates how to manage and optimize IIS pools for running ASP.NET apps.

Prior to .Net 3.0 it was not an easy matter to select a particular technology for communicating between systems due to the number of technologies available from  Microsoft. For example, users could have used Web Service to communicate between a Java based application and a .Net application; WSE users  could have take advantage of some [...]

SQL Server Optimizer, Under the Hood – Partial Aggregates Abstract: In this series of short articles, we lift the hood of the SQL Server Optimizer to examine a few of the many clever tricks used to optimize query performance.  You’ll see that the Optimizer does not limit itself to using only the instructions provided by [...]

 Introduction Data Compression was first introduced in SQL Server 2005 with Service Pack 2 when Microsoft introduced a new storage format called VARDECIMAL to store decimal and numeric data types as variable length columns. In SQL Server 2008, Microsoft enhanced Data Compression feature to compress fixed length data types such as INTEGER, CHAR and FLOAT. [...]

Detailed guide to shared, VPS and dedicated hosting.

Introduction One of the most important responsibilities of a database administrator is to make sure that all the databases are backed up across environments managed by them. In my earlier article titled Importance of Database Backups and Recovery Plan I discussed the importance of a good database backup and recovery plan for all the user [...]

Under a DAG configuration,  mailbox data is replicated across several hosts.  The result of this is that in Exchange Server 2010 it is now less important to build in system level redundancy. If a DAG node fails, as opposed to  rebuilding it, we can simply build a node, add it as a replica, the data will replicate to it.