Additional Articles


Technical Article

Joining to the Next Sequential Row

One of the more obscure requirements that a developer may find themselves facing is the need to compare a row with its immediate sibling. One such case is when a list of values needs to be processed to produce a moving average or to smooth a sequence of statistical numbers where their order is important. For example, values lying along a time line. The solution is actually quite simple, but not immediately obvious.

(3)

You rated this post out of 5. Change rating

2008-04-10

4,439 reads

External Article

SQL Server Tracing: An Automated and Centralized Solution

When you are trying to pin down the cause of a problem with a SQL Server, there is probably going to come a time when you need to get 'trace' information. If you've ever done that, you'll know how easy it is to get overwhelmed by the detail. Here, Shawn McGehee shows how to get round the problem by capturing trace information on a schedule, filtering the captured information, and monitoring it from a central location.

2008-04-09

2,451 reads

Blogs

New article – migrating from a named instance

By

Do you have a case where you have a named instance you'd like to...

Using the SIGN() Function: #SQLNewBlogger

By

I was trolling the docs and noticed the SIGN() function. I have never written...

T-SQL Tuesday #201 Round-Up: Temp Tables, Friend or Foe?

By

The T-SQL Tuesday #201 round-up: nine bloggers on whether temp tables are a friend...

Read the latest Blogs

Forums

Admin Rights for Everyone

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Admin Rights for Everyone

Kerberos Authentication for Aurora PostgreSQL: Mapping AD Groups to Database Roles

By Arvind Toorpu

Comments posted to this topic are about the item Kerberos Authentication for Aurora PostgreSQL:...

RegEx Functions I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item RegEx Functions I

Visit the forum

Question of the Day

RegEx Functions I

Which of these RegEx functions need compatibility level 170 in SQL Server 2025?

See possible answers