local_phone(877) 456-7632 local_post_officeinfo@msxgroup.com
Message Boards
Sign up Latest Topics

  Author   Comment  

Posts: 88
Reply with quote  #1 
For performance reasons, Forecaster and Forecaster Web Access will often create temporary tables in the Forecaster database.  These tables have various names but usually follow the pattern of:  a 4 or 5 letter name, the current date and time, the username.  So, an example might be:


This is the "Z_BUD" temporary table, created on July 2, 2010 at 16:45:37.529 by the user whose username begins with "ROBD"

There are many different temporary tables created by Forecaster, Forecaster Web Access or the Excel Add-in, but they all follow this pattern and naming convention, which is very different from the standard, permanent Forecaster tables.  In addition, these tables will usually be listed with a different owner in the database (the actual Forecaster user as opposed to dbo).

Typically, Forecaster is good about removing these tables when a user logs out or when the system is finished using the screen.  But sometimes the tables get left in the database.  There are numerous reasons for this, but the main ones are: 

1. A save was still in progress when the user logged out, so Forecaster did not remove the table in case it was still needed.

2. The user had more than one Forecaster session open, so neither one  could do the cleanup work without the potential of removing temporary tables from the other session.

3. Forecaster exited abnormally, due to a product flaw, a network failure, a hardware failure or other reasons.

4. The user killed the Forecaster session by using Windows Task Manager to end the process.

To cleanup these tables:

1. The Forecaster administrator should have everyone log out of Forecaster (including the administrator). 

2. Then, the administrator should log back in and go to Tools | Validate Database. 

3. Choose the Zap Event Log and Re-index Tables options.  Do NOT choose any other option on this screen.

4. Click OK.

5. When the process completes, the administrator should log out.

At this point, the temporary tables should all be gone.

It is important to note that while users are logged into Forecaster, Forecaster Web Access or the Excel Add-in, temporary tables will be in existence.  This is why it is important to have everyone logged out -- so that no active sessions will have their temporary tables removed unexpectedly.

Rob Diaz
MSX Group
Previous Topic | Next Topic

Quick Navigation:

Easily create a Forum Website with Website Toolbox.