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,179 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,467 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

Blogs

Are you getting value from your reporting?

By

Do you spend so long manipulating your data into something vaguely useful that you...

The Book of Redgate: SQL Server Central

By

It was neat to stumble on this in the book, a piece by me,...

Git forked

By

Forgive me for the title. Mentally I’m 12. When I started my current day...

Read the latest Blogs

Forums

Microsoft Security Changes and SQL Server

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Microsoft Security Changes and SQL...

Expanding into Print

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Expanding into Print

Downtime Caused by the Postgres Transaction ID Wraparound Problem

By Chandan Shukla

Comments posted to this topic are about the item Downtime Caused by the Postgres...

Visit the forum

Question of the Day

The String Distance I

In SQL Server 2025, what is returned by this code:

SELECT EDIT_DISTANCE('Steve', 'Stan')
Assume preview features are enabled.

See possible answers