OK. I think I somewhat understand now. The thing is, you're going to NULL values, you have to. You have a mismatched set of rows across the tables, so some...

Never tried that. I'd just uninstall and reinstall. Safer that way.

So, I'm unclear how your tables map together. What are the primary and foreign keys that define the relationships. That ought to drive us towards a meaningful query. As it...

Stefan Krzywicki (5/12/2014)

---

Ed Wagner (5/12/2014)

---

Stefan Krzywicki (5/12/2014)

---

TomThomson (5/12/2014)

---

Ed Wagner (5/12/2014)

---

Sean Lange (5/12/2014)

---

Lynn Pettis (5/12/2014)

---

Sean Lange (5/12/2014)

---

Ed Wagner (5/12/2014)

---

It sure is nice to hear that others remember the old "alt codes"....

Didn't the query show you what was in the memory? It came from somewhere on the system within your SQL server instance. Maybe it's just all index maintenance scripts that...

I do occasionally have reading problems. And this was one of them. Apologies.

Of course, the function on that column will preclude index seeks.

I'm with Gail. I'm just guessing without an execution plan.

And joining millions of rows is more costly than simply selecting millions of rows. That's just how it works. Joining 2...

Without seeing the execution plan we're just guessing, but this index:

pk_ss_pLevelID clustered, unique, primary keylocated on PRIMARY pLevel, pLevelID

Strikes me as potentially problematic. What does the data in pLevel look...

You can just go and look at it. Here's a blog post from Microsoft that shows how.

Even if the database hasn't been touched for weeks, if it was in use,...

I'd say, test it out and see how it works. The inserted table is available from a trigger. As long as you designate it as an AFTER trigger... test it.

SQL Server will just fill the memory on a machine right up to the limit you give it, or, to the point where it contends with the OS for memory....

For the test to past, both records have to be there, so you can't really automate it from the database end since either record could be missing at the moment...

I think I would probably do this programmatically. I mean, if you tried using a trigger that stopped inserts of an A type row unless there was already a B...

Back to an area that I'm not sure about. I don't know.