I'd say that Cool Sig's response was pretty close to what I would do:
DECLARE @BenchTest TABLE
(ID INT IDENTITY
,PartNumber INT
,PartName VARCHAR(10)
,TestDate DATETIME);
INSERT INTO @BenchTest(PartNumber, PartName, TestDate)
VALUES(1,'A','2012-01-01 11:00'),(2,'B','2012-01-01 12:00')
,(3,'C','2012-01-01 13:00'),(4,'D','2012-01-01 14:00')
,(1,'A','2012-01-02 12:00'),(2,'B','2012-01-02 13:00')
,(3,'C','2012-01-02 14:00'),(4,'D','2012-01-01 15:00')
,(1,'A','2012-01-03 12:00'),(2,'B','2012-01-03 13:00')
,(3,'C','2012-01-03 15:00'),(4,'D','2012-01-01 15:00')
,(1,'A','2012-01-04 12:00'),(2,'B','2012-01-04 12:00')
SELECT ID
,PartNumber
,PartName
,CycleNum=ROW_NUMBER() OVER (PARTITION BY PartNumber ORDER BY ID)
,TotalCycle=COUNT(*)Over(Partition by PartNumber)
,TestDate
FROM @BenchTest
ORDER BY PartNumber
The main difference being to order by ID in the ROW_NUMBER().
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St