Can temporary files used in table maintenance (eg optimisation) be given a name that will allow the table to be identified please. I just had a "senior" moment and clicked the icon to close the PC down whilst it was busy optimising. I am assuming that the new table is built then the original deleted and the new ones renamed but it would be nice to be able to check.

Roy Lambert

Roy,

<< Can temporary files used in table maintenance (eg optimisation) be given
a name that will allow the table to be identified please. I just had a
"senior" moment and clicked the icon to close the PC down whilst it was busy
optimising. I am assuming that the new table is built then the original
deleted and the new ones renamed but it would be nice to be able to check.
>>

If the optimization process didn't succeed, then the original files should
be intact.  If they aren't, then the .old file backups should have a new
date/time stamp and will be the original files.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


><< Can temporary files used in table maintenance (eg optimisation) be given
>a name that will allow the table to be identified please. I just had a
>"senior" moment and clicked the icon to close the PC down whilst it was busy
>optimising. I am assuming that the new table is built then the original
>deleted and the new ones renamed but it would be nice to be able to check.
> >>
>
>If the optimization process didn't succeed, then the original files should
>be intact. If they aren't, then the .old file backups should have a new
>date/time stamp and will be the original files.

That's what I assumed, but the temporary tables created give no indication of which table was involved ie just the normal temporary table naming system eg WORKDELL88847401163268NLH1 rather than CompaniesBeingOptimisedTemporaryTable or something

Roy Lambert

Roy,

<< That's what I assumed, but the temporary tables created give no
indication of which table was involved ie just the normal temporary table
naming system eg WORKDELL88847401163268NLH1 rather than
CompaniesBeingOptimisedTemporaryTable or something >>

That's just it - you don't want those files.  If the temporary file was not
copied back to the original (creating an .old beforehand), then it can just
be deleted because it's junk.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

><< That's what I assumed, but the temporary tables created give no
>indication of which table was involved ie just the normal temporary table
>naming system eg WORKDELL88847401163268NLH1 rather than
>CompaniesBeingOptimisedTemporaryTable or something >>
>
>That's just it - you don't want those files. If the temporary file was not
>copied back to the original (creating an .old beforehand), then it can just
>be deleted because it's junk.

I know that, but I'd still like to know which table was being worked on. One benefit would be that I could then restart the process at the appropriate point rather than having to run through it all again. This could save me an hour or more.

Roy Lambert

Roy,

<< I know that, but I'd still like to know which table was being worked on.
One benefit would be that I could then restart the process at the
appropriate point rather than having to run through it all again. This could
save me an hour or more. >>

Okay, I'll have to look into this further to make sure that I'm not setting
EDB up for a conflict by doing this.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>Okay, I'll have to look into this further to make sure that I'm not setting
>EDB up for a conflict by doing this.

Thanks. I had thought of a log file, but since the "problem" was caused by me turning the PC off when it was running I wasn't sure it would work, but I've just realised I can close it off between each table then its just down to the OS getting it to disk. So if altering the names would be a hassle don't bother.

Roy Lambert