Articles

External Article

Cycling the ERRORLOG file and Deleting Backup History Information

Every DBA needs a few tricks up his/her sleeves to help them better manage their SQL Server 2000 environment. In this article I will explore a couple of such tricks. I will first explore how to cycle the SQL Server error log, and why you might want to do this. Secondly I will discuss backup history information and why you would need to periodically remove some of the older history information.

2006-03-16

2,855 reads

SQLServerCentral Article

An Error Handling Template for 2005

One of the big complaints in SQL Server development has been error handling. SQL Server 2005, however, substantially enhances its capabilies in this area and Leo Peysakhovich brings some code that provides a template for adding error handling to your application.

(8)

You rated this post out of 5. Change rating

2006-03-14

19,172 reads

External Article

Practical SQL Server 2005 CLR Assemblies

One advantage of CLR assemblies is the ability to consume web services from within the database. This wouldn’t be easy with T-SQL, and would also require a lot of work in an unmanaged extended stored procedure. With .NET, it’s almost as simple as accessing a local DLL. There are just a couple of extra command-line utilities we need to run to be able to access web services from within a SQL assembly:

2006-03-14

3,849 reads

SQLServerCentral Article

Differential Backup Prediction

SQL Server 2000 has a rock solid backup scheme , but do you really need to run full backups every day? What if you could decide on the fly if it was more efficient for a full or a differential backup? Darwin Hatheway brings us the basis for a scheme that can predict the size of a differential backup by examining how much of the database has changed.

(3)

You rated this post out of 5. Change rating

2006-03-13

7,461 reads

External Article

Try/Catch Block in SQL Server 2005

Server 2005 now supports a more programmable error trapping convention in T-SQL code. This error handling is known as the TRY/CATCH block. The TRY/CATCH block allows T-SQL to handling errors like other programming languages, such as Microsoft Visual C# and C++. In addition to the TRY/CATCH block, Microsoft has expanded the set of available system functions in SQL Server 2005 for returning error codes and messages when an error occurs in your T-SQL code. This article will explore the new TRY/CATCH block and explain the new system functions for returning error codes and messages.

2006-03-13

3,150 reads

External Article

SQL Server and .NET Training and Career Development

In the past, it was common for an employer to work with their employees and pay to keep their skills current. While this still happens, in this age of high employee (and employer) turnover, many companies are more circumspect about how much they will spend to keep their employees keep up-to-date. At the end of the day, it is your responsibility to make sure this happens and there are many good reasons why you should strive to do so and many ways in which you can do it.

2006-03-09

3,546 reads

Blogs

Enterprise AI Operating Rhythm – Top 5 practices for 2026

By

2025 exposed a growing gap between AI ambition and operational reality. As budgets tightened...

Resetting on the AI hype train

By

There's a great article from MIT Technology Review about resetting on the hype of...

A New Word: Etherness

By

etherness – n. the wistful feeling of looking around a gathering of loved ones,...

Read the latest Blogs

Forums

The Max PK Length

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Max PK Length

My experience using the GitHub Copilot in SSMS 22

By Daniel Calbimonte

Comments posted to this topic are about the item My experience using the GitHub...

The Microsoft SQL Year in Review

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Microsoft SQL Year in...

Visit the forum

Question of the Day

The Max PK Length

If I create a multiple column Primary Key constraint, what is the most number of bytes I can include in the constraint?

See possible answers