Might be a recursion problem with the sub-query.

I have to ask, why the sub-query at all, or are these two different tables?

Are you using a GUI table designer in VS?

If so, the way most of those work is by creating a temp table, loading all the data from the table into...

vbradham (12/9/2010)

---

It amazes me that questions get asked, and yet no-one answers the questions. I would find so useful the example asked for here.

Leave the error checking aside, I...

Fraggle-805517 (12/10/2010)

---

Hello everyone. Got a bit of a challenge. All code for testing is below. What I am looking for is kinda a running total. For...

On the schemas, you can check the schema_id column in sys.all_objects.

On performance, I'd run perf mon for a bit before and after, and see what the numbers look like.

Honestly though,...

I tend to avoid comma-delimited lists for parameters these days, but when I do use them, I often find it useful to insert them into a temp table as the...

It'll take a cursor to do multiple tables efficiently. You could use sp_MSForEachTable, but that's just a hidden cursor.

Zeev Kazhdan (12/10/2010)

---

Interesting article, but I have a question, which hopefully will save me a lot of hours:

In Oracle 10 I do it in one select statement, using START WITH...

autoexcrement (12/10/2010)

---

Fascinating article! I have a couple of naive questions about the following bit of G code:

Adjacency (NodeID, ParentID) as -- Adjacency Query

...

Craig Farrell (11/19/2010)

---

Hey Gus,

Late to the party, I know, but you referenced this in another thread and I had a curiousity. Could you discuss the 'lazy updater' component a...

Then you'll need to drop them explicitly.

Those errors mean you didn't name the derived table "CTE1". That's all.

Are you writing a stored procedure?

If so, you don't need to explicitly drop the temp tables. The whole point is that they'll go away when the connection closes at...

GilaMonster (12/10/2010)

---

GSquared (12/10/2010)

---

I'll add to the question: Should autoshrink be removed, and then put back in when SSDs become the standard and hard-drive seek time is no longer a problem...

I'll add to the question: Should autoshrink be removed, and then put back in when SSDs become the standard and hard-drive seek time is no longer a problem that needs...