Hi!

We are facing major speed issues in finance. A database review was done suggestions given:

H/W upgradation
Session specific changes

The third issue was that in Finance no of records in certain tables are two high ... namely tfgld106 and tfgld410. I know for reducing no. of records in tfgld106 aproper archiving needs to be done....

But for tfgld410there is session to Purge ntegration transaction. we have never done it here in our organization.. Would any one plz tell what is the loss of information that may occur if we do the same...


any other experiances which help in speed issues??


Rgds,


Himanshu

Unfortunately it is not as easy as just archiving within finance as the finance archiving sessions depend upon other archiving sessions being run first.

I would really advise that you implement a full archiving strategy to assist with your performance problems.

Please be aware that in a lot of cases data is actually moved into the archiving company and not lost ie. you can archive integration transactions as opposed to purging them.

The attached document should be a good starting point.

Regards
Neal Matthews

thanx a lot for the document. It will be really useful... we plan to strategically go abt with archiving as a project .

Rgds,

Himanshu

Hi Himanshu,

I assume u r getting performance problems in most of your sessions. If this is the case then i have some tips..if this is not the case and performance is only with a few sessions then archiving and fine tunning your scripts with correct select and indexes is needed.

To improve overall performance u need to concentrate more on the D/B and your networking again assuming your Servers have been sized adequately.

- Recalculation of initial and subsequent extents of hot tables/indexes
- Recreation of sysmaster tables is also necessary for the same reason, but it requires reinstallation of the D/B server.
-Separate dbspaces to be created for hot tables so as to speed up the server database actions.
- Fragmentation
- database logging mode buffered one gives very good response.

Pls discuss these issues with a good and confident D/B administrator.

Hi ral

As advised we have done a proper Db review and the suggestions given by you were one of the major considerations during the same.

Extents have been reduced from >140 to around 1, hot tables in seperate dbsapce as well as discs,buffers checked.

End result was limitation of RAM as present RAM is 4GB but advised is atleast 5 for the data..

We are looking for new server setup and upgradation...


But alongwith , voluminous tables like tfgld410,418 have to be reduced. So we need to Archive the same.


Thanx for the Info...

Himanshu