SQL Server Denali THROW statement to raise an exception

Raising exception with THROW statement in SQL Server Denali

Prior to SQL Server 2005, writing code for exception handling was painful for T-SQL developers. SQL Server 2005 introduced structured exception handling with BEGIN TRY...BEGIN CATCH blocks. Though this inclusion made managing exceptions in T-SQL programming quite easier, it has some limitations. In this tip I am going to talk about some of these challenges and limitations, then show how a new command THROW in SQL Server Denali overcomes those items, click here for more info.

Understanding Ad-hoc paging in SQL Server Denali

SQL Server Denali Server Side Paging

When designing a User Interface (UI) you normally display 10, 20, 50 or 100 rows on the screen for readability purposes and easy navigation. One way to do this, is to bring all the data from SQL Server to local memory and do the navigation locally. This approach looks simple, but has a couple of issues. First, it could choke the network during a huge data transfer from the server to the local machine (or machine running UI). Second, you could need much more memory to accommodate the data locally. Third, when you navigate to the next page you are actually viewing data stored locally and you will not be able to see updated records on the server until you re-fetch all the data again. So what are some options for server side paging and how does SQL Server Denali improves on this process? Check out this tip to learn more.

Diagnostic logging in SharePoint 2010

For diagnostic logging, the Unified Logging Service (ULS) has been available since previous versions of SharePoint. But what improvements and refinements have been done in SharePoint 2010? What are the options available for diagnostic logging in SharePoint 2010? How better we can control the amount of diagnostic information to be logged in SharePoint 2010? For more details click here.

Getting Started with the SharePoint Logging and Reporting Database in SharePoint 2010

In my last tip I talked about diagnostic logging in SharePoint 2010 and how it helps in troubleshooting. Troubleshooting with trace files is good but wouldn't it be cool if we have all the logging (usage and health) information on single place in consolidated form which help you to build reports and do analysis on collected data from all the servers of the farm? I heard SharePoint 2010 has new logging database. What is it, what does it store? How we can control the amount of information to be logged in the SharePoint logging database? For more details, click care.

Health Analyzer in SharePoint 2010

As a SharePoint Administrator you always wanted to have something in place which alerts you about the running issues or potential problems in your farm. SharePoint 2010 has come up with an 'out of the box' Health Analyzer feature which alerts you about the potential problems, and the locations where they occurred, the cause and how to resolve these issues. Let's explore it more.

Getting started with Code Snippets feature of SQL Server Denali

In SQL Server Denali under Manageability enhancements, code snippets feature has been introduced. In this tip I am going to talk about what it is, how to use it and if required how can we customize/add code snippet (script template) as per our need, for more details click here.

Short-cut keys for commonly used tasks in SSMS - Part 2

We often overlook different SSMS shortcut keys which provide a boost in DBA and Developer productivity. In the second tip of this series (SQL Server Management Studio keyboard shortcuts - Part 1), I am going to further explain shortcut keys for managing Intellisence, debugging, running your code and many more...click here