Friends,

Three questions for you:

1. Are CREATE INDEX statements against DGTTs logged?

2. In what circumstances would you expect to see, upon killing an
UPDATE *against a DGTT*, an Application Status of "Rollback Active"? I
have to say I'm stumped by this, but that's exactly what I'm seeing. I
forced an agent that was running a stored procedure that contains only
UPDATEs and INSERTs against DGTTs (honest--I've checked and re-
checked; they're all SESSION and declared as NOT LOGGED), and when I
do "get snapshot," I see the following:

Application status = Rollback Active
Start Time = 10/04/2007 16:26:25.841347
Completed Work = 777939793 bytes
Total Work = 2125582205 bytes

Lat night I got a "transaction log filled" message, and thought it may
have been caused by one of my index CREATEs against a DGTT coupled
with bad timing (i.e., concurrent user taking all of the log space),
hence my first question. But based on what I've seen that led me to my
second question, I think the plot has thickened.

3. Is there any point (performance-wise or other) to COMMITing INSERTs
and UPDATEs against DGTTs?

--Jeff