Christoffer Hedgate

I work in Lund, Sweden, at a company called Apptus Technologies. Apptus are specialized in database research and consulting, including development of search engines. Most of the time I work with SQL Server as an architect, administrator and developer, but I have also done some work with other DBMS such as Oracle and TimesTen. I also do some programming, mainly in Visual Basic, C# and Java (plus a couple of scripting languages).

I am also the co-owner of sql.nu (http://www.sql.nu/) where you can find more articles from me.
  • Interests: Movies, sports, databases, games

SQLServerCentral Article

Dynamic Management Objects

These are not the DMO bits you are thinking of from SQL Server 2000. SQL Server 2005 introduces a new way of digging into the inner workings of the server with both Dynamic Management Views and Dynamic Management Functions. Longtime SQL Server guru Christoffer Hedgate looks at these new ways of understanding your server.

You rated this post out of 5. Change rating

2006-01-26

9,027 reads

SQLServerCentral Article

Measuring SQL Performance

One thing that often amazes me is that many SQL Server developers do not actually measure the performance of their queries. Many of them thought that you needed external tools, more or less complicated, to run against your server, and they did not have the time or inclination to learn and try these. This article will describe a couple of much easier methods of measuring performance of queries.

(5)

You rated this post out of 5. Change rating

2005-12-23 (first published: )

37,769 reads

SQLServerCentral Article

CLR Integration

One of the more controversial new features in SQL Server 2005 is the inclusion of the Common Language Runtime (CLR) inside the server. Whether you agree this is a good idea or not, the very knowledgable Chris Hedgate brings us the first article in a series looking at how the CLR fits into your database server.

(4)

You rated this post out of 5. Change rating

2005-07-13

17,244 reads

SQLServerCentral Article

On the Trail of the ISO Week

Chris Hedgate, one of our regular SQL Server columnists, recently became intrigued by the way that SQL Server implements the week number. His concern was why SQL Server treats week 53 as week 1, which is not that way that ISO6801 sees it. Read about his investigation into the methods of implementing an algorithm to solve this problem.

(3)

You rated this post out of 5. Change rating

2005-01-20

11,661 reads

SQLServerCentral Article

Moving System Databases - A Checklist

The default location for the SQL Server system databases doesn't always meet the standards of many organizations. Author Chris Hedgate has taken the time to put together a short checklist on how you can move the master, msdb, model, and tempdb databases easily.

(4)

You rated this post out of 5. Change rating

2004-11-30

21,847 reads

Blogs

A Wellbeing Day at Redgate

By

It’s a day off for Redgate today. This is our annual wellbeing day, where...

Don’t Miss Out – SQL Server 2025 Unleashed Training Starts Next Monday!

By

Next Monday, March 9, 2026, my one-day live online training SQL Server 2025 Unleashed:...

What is ALM in Fabric?

By

As someone who’s worked with data for over 20 years and with many cloud...

Read the latest Blogs

Forums

A Quick Restore

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Quick Restore

Guarding Against SQL Injection at the Database Layer (SQL Server)

By Terry Jago

Comments posted to this topic are about the item Guarding Against SQL Injection at...

Ola Hallengren Index Optimize Maintenance can we have data compression = page

By JSB_89

I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...

Visit the forum

Question of the Day

A Quick Restore

While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:

USE DNRTest

BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO
/*
Bunch of stuff tested here
*/RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACE
What happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance.

See possible answers