32Bits

16GB RAM

/PAE

AWE Enabled ...

Thanks. Was already resolved, but you code also works.

Steve Jones - SSC Editor (3/3/2014)

---

I haven't typically seen connection issues taking many resources in SQL2K5+ instances. In SQL 7, it could be an issue, but usually in the 1000s...

Your question is a bit unclear.

Take a look at this handy article.

http://weblogs.sqlteam.com/jeffs/archive/2008/05/13/question-needed-not-answer.aspx

Is this a 32 bit system? The memory pools used by SQL Server in a 32 bit system sometimes needed help. Especially if you were moving around a lot of...

Bingo!

Here's the full code. (Sample data, 2012 query, 2005 sub queries, 2005 cte).

Is this also possible using some advanced APPLY tricks?

USE TempDB

GO

IF OBJECT_ID('#CumDiffs') IS NOT NULL

DROP TABLE #CumDiffs

CREATE TABLE #CumDiffs

(

IDSmallInt...

The result of each the queries differ.

Here is some sample data. 10 rows to easily check the results.

USE TempDB

GO

IF OBJECT_ID('#CumDiffs') IS NOT NULL

DROP TABLE #CumDiffs

CREATE TABLE #CumDiffs

(

IDSmallInt IDENTITY,

SampleDateTImeSmallDateTime,

DriveLetterChar(1),

SampleValueSmallInt

)

INSERT#CumDiffs

(SampleDateTIme, DriveLetter, SampleValue)

SELECTTOP...

I added an Identity(1,1) to the StallsHistory table and made it the cluster PK.

The join now uses S1.SurroID = (S2.SurroID - 1) AND S1.Drive = S2.Drive

This looks pretty close to...

Thanks for your response Jack.

Your query works fine, but does not return the results i am looking for.

I'm want to see the difference between each row record. i.e. Row2value -...

Thanks for responding.

Was afraid someone would say something like that.

Time to plan the downtime.

Thanks.

You could create a job and schedule it to run on SQL Server Agent start up.

If you have nolock, then you have the potential for dirty reads, duplicate rows and missed rows and it doesn't matter (for the latter 2) that each process works on...

It's been a week now.

NOLOCK hint did the trick.

No more deadlocks with this process.

No dirty read issues.

Thanks for the help guys.

Dirty reads shouldn't be an issue. Each process only...

Can you convert the process to be a single stored procedure? The set for printing wouldn't be a problem, there are a variety of ways to handle it. Your options...