Definitely don't have those entries on my server.

Is it possible the server didn't do a clean shutdown? Like sudden loss of power or anything like that? It might...

I rebooted my desktop yesterday morning. ...

CptCrusty1 (8/28/2012)

---

@Laurie, Mark, GSquared. I am humbled.

I was starting to lean towards Cross Join; however, I'd never had an opportunity to use it before. Seems like it behaves...

laurie-789651 (8/28/2012)

---

GSquared (8/28/2012)

---

That's what's called a "Table Values Function", and it's...

The first mistake that comes to mind is that you shrank the database after rebuilding the indexes, per the last line of your post. That will slow queries down...

That's what's called a "Table Values Function", and it's 2008+. ...

I did a big-table test on a couple of these.

Test-harness:

CREATE TABLE dbo.SequenceSkips

(Num1 INT NOT NULL,

Num2 INT NOT NULL,

...

Lynn Pettis (8/28/2012)

---

Here is my shot at the solution.

CREATE TABLE #Temp

(TNID INT, TN BIGINT);

INSERT INTO #Temp

SELECT 3011170, 4402787100

UNION ALL SELECT 3011170, 4402787101

UNION ALL SELECT 3011170, 4402787102

UNION...

As an alternative (sorry for the fragmented posting, it's been a long day), you might want to look into what those jobs are doing, and see if there's a better...

That's a system update. I don't think there's really anything you can do about it directly.

Depending on what else the server is used for, you might relieve cache-pressure by...

It probably means you're trying to insert an explicit value into an ID column, without turning on Identity Insert first.

Without seeing the definition of the destination table, and the insert...

Since the data depends on sequentiality, which isn't a property of relational data, you'll need a non-relational solution. That means a simple cursor.

Step through the rows, if the TN...

Eugene Elutin (8/28/2012)

---

...

You can slightly simplify this be leaving out the Group By clause in the subquery. It's not necessary, since the Where clause already enforces a distinct value....

I know. That's part of what "You'll see what it does for yourself" was...

I get a floating point error instead of a domain error, but I'm using SQL 2008 R2, so maybe they just changed the error message for this type of thing.

By...