Re: Problem with Temp Tables and Logging

Mark, try the following: select * from table into temp t1 WITH NO LOG; should speed up your query and save some log space as well. Apparently-To: RZBJ40@email.sps.mot.com We are encountering a curious situation: A query is run that creates a temporary table (implicit). It ran fine for quite a while, but now we get -458 (long transaction aborted). I know that we need to create a tempdbspace (right now it all goes into our rootdbs), but the temporary table data is small (only 10K of data). We have about 150Mb free, and our logs are 400K x 40 files. We do go through the log files quickly (about every 45 seconds). Is it possible that the query starts, then the logs roll right around and the query, not being completed, gets the boot? It is only a select, but it does contain ORDER BY, and that phrase is causing the query to take forever to run. Has anyone seen anything like this before? Also, I have another database that has so little space, that the oninit fails because pages cannot be allocated. If I perform an oninit -s, can I get up enough to add a chunk? Thanks in advance... Mark Christmas CrossKeys Systems Corp