Advanced Querying

SQLServerCentral Article

SQL Window Functions Series: NTILE()

  • Article

Unlock the power of SQL's NTILE function with our latest deep-dive article. Learn to segment your data effectively into quantiles for more nuanced analysis, discover common pitfalls and their solutions, and optimize your queries for peak performance.

4.67 (3)

You rated this post out of 5. Change rating

2024-02-03 (first published: )

4,828 reads

SQLServerCentral Article

5 (4)

You rated this post out of 5. Change rating

2023-11-20 (first published: )

12,457 reads

Technical Article

Why Read-only Table Parameters is Not Enough

  • Article

In this article I discuss a new feature in SQL 2008, table-valued parameters and particularly the restriction that they have to be read-only. I argue that this makes this feature considerably less useful that it could be, and that in order to build scalable applications be able to pass read-write table parameters between stored procedures is essential.

2008-04-02

2,677 reads

SQLServerCentral Article

SQL Server 2008 - The Power of Merge

  • Article

We have a first look at one of the features in SQL Server 2008 that was cut from SQL Server 2005, but which has been highly anticipated. How many times have you written an "insert new, update match" routine? Jacob Sebastion shows us easy this becomes with the new MERGE keyword in SQL Server 2008.

4.8 (5)

You rated this post out of 5. Change rating

2007-09-11

14,046 reads

SQLServerCentral Article

Server Side Paging With SQL Server 2005

  • Article

One of the more common requests of an application working with SQL Server is to deal with pages, or sections, or data rather than an entire result set. Often an application retreives the entire result set and then only shows the user a few records, repeating the process with the next page. Regular columnist Jacob Sebastian brings us a more efficient method of implementing paging in SQL Server 2005.

4.86 (7)

You rated this post out of 5. Change rating

2007-08-29

13,685 reads

SQLServerCentral Article

Getting Random Results

  • Article

One common need that DBAs run into is building a report that returns data in some random order. Especially if you're doing some type of contest, like giving something away at your User Group meeting. Andy Warren brings us a short article on this with a look at the performance impact of randomly ordering results.

5 (2)

You rated this post out of 5. Change rating

2007-08-23

4,344 reads

Blogs

Cloud Data Driven User Group 2025 – Slides & Scripts

By

The slidedeck and the SQL scripts for the session Indexing for Dummies can be...

Leading Through Change: Guiding Teams in Times of Uncertainty

By

Change is not a disruption in technology; it is the rhythm. New frameworks appear,...

The Mystery of the Locked-Up Database -Scooby Dooing Episode 6

By

No Scooby-Doo story is complete without footprints leading to a hidden passage. In SQL...

Read the latest Blogs

Forums

Don't Forget About Financial Skills

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Don't Forget About Financial Skills

Building a Simple SQL/AI Environment

By Tony Savoie

Comments posted to this topic are about the item Building a Simple SQL/AI Environment

Checking Identities

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Checking Identities

Visit the forum

Question of the Day

Checking Identities

The DBCC CHECKIDENT command is used when working with identity values. I have a table with 10 rows in it that looks like this:

TravelLogID CityID  StartDate   EndDate
1           1       2025-01-11  2025-01-16
2           2       2025-01-11  2025-01-16
3           3       2025-01-11  2025-01-16
4           4       2025-01-11  2025-01-16
5           5       2025-01-11  2025-01-16
6           6       2025-01-11  2025-01-16
7           7       2025-01-11  2025-01-16
8           8       2025-01-11  2025-01-16
9           9       2025-01-11  2025-01-16
10          10      2025-01-11  2025-01-16
The docs for DBCC CHECKIDENT say this if I run with only the table parameter: "If the current identity value for a table is less than the maximum identity value stored in the identity column, it is reset using the maximum value in the identity column. " I run this code:
DELETE dbo.TravelLog WHERE TravelLogID >= 9
GO
DBCC CHECKIDENT(TravelLog, RESEED)
GO
INSERT dbo.TravelLog
(
    CityID,
    StartDate,
    EndDate
)
VALUES
(4, '2025-09-14', '2025-09-17')
GO
What is the identity value for the new row inserted by the insert statement above?

See possible answers