Done with nested cursors (curses!)

Does not significantly hinder perf -- in dev.

Now, let's try running 30 times a minute, with 250 users!

mwah-ah-ah-ah-ah-ah

BTW: Rows 7 and 8 should be as follows (I forgot to increment the nLevels).

INSERT tmp_list VALUES (7, 3, 'SubSubHeading1')

INSERT tmp_list VALUES (8, 4, 'DetailA')

What I'm trying to do is...

There were also NINJA loans: No Income, No Job, No Assets (collateral).

Really now, who in their right mind could think these would ever be repaid, regardless of what the models...

It comes down to the first acronym I ever learned having to do with computers and computing: GIGO -- Garbage In, Garbage Out.

True for both data and code, which always...

re: Definitions

In my mind, the data model *is* business logic incarnate. The objects and relationships expressed though the model's design are nothing if not business logic. (I'm not saying that...

John,

Looks like you hit it with the SET options. Closer inspection revealed that SET ANSI_WARNINGS was ON for QA, OFF from app.

Changing that made the difference.

Steve,

Running everything...

This weekend, I came upon the definition of kludge. The following is from Wikipedia: In modern computing terminology, a kludge (or often a "Hack") is a 'solution' to a problem,...

Indexes rebuilt for the second time in 2 hours.

What took 20 minutes earlier today -- but after the same index rebuild 2 hours ago -- now returns in...29 seconds!!!!!

My head...

Only difference in SET options is Quoted Identifiers on for QA, off for app.

All others identical.

Now, running same reports, but for a shorter time period: 20 minutes and counting both...

How do I see the query plans?

"It (always) depends", and I've found it's poor performance and complaints from users that tends to focus the DBA's mind.

After a few episodes, thinking begins.

P

On the other hand, many-to-many join tables, for example, I would never put a identity in again. (I did, several times, when I new to databases. Regretted it later every...

When Newfoundland (NF) changed it's official name to Newfoundland and Labrador (NL), the use of a natural key meant a 25 million row update, and weekend work to do it.

I'd...

Sergyi: Bwahahahaha! Spot on!!! It's an even safer bet when it's the users who come saying, "It'll never need to {fill in whatever here}".

Another reason to put business logic in...

Well, it looks like bad app code: there were several hundred open transactions, and the server was simply chocking on the load.

Adding commits after read operations solved the problem.