baanprog
19th May 2005, 17:40
Hi,

We have tfgld106 with 80GB data and we want to increase access times for session.

Request your comments. Reconfig takes days if we add indexes........

Regards

norwim
20th May 2005, 01:45
Hi there,

I have to admit that I am not at all experienced with finance, but I recall some faint memories concerning the impacts of integration of finance package with other packages.
I think that the amount of data that will be written to some tf-tables is specified by your finance-integration-parameters.
Hopefully someone on the board will give more detailed info here, but unless all your tables are that incredible large, I would assume that tuning these integration parameters can help you to reduce the size of tfgld106.

Good luck

Norbert

lakoon
20th May 2005, 17:22
Hello

You can reduce the amount of data by archiving the finance transactions. The data will be copied to the archive company and the running environment shrinks (after reorg...)

/lakoon

richard
23rd May 2005, 18:17
Hello,

We don't use all dimensions and are using Oracle level 2.
So we dropped physically the index 7 and 8.
Only tfgld1407 session was to change.

At the beginning of BaaN we didn't compress the data, the size was also up to 18 Go.
Now it's archieved.

Regards

dave_23
23rd May 2005, 20:57
Why would you drop indexes? are you worried about "insert" transactions
or "select" transactions?

You may not be using those dimensions - but the Baan code might not
care and try using those indexes anyway. Dynamic SQL doesn't exist in Baan 4.. only Baan 5.

Dave

lakoon
24th May 2005, 09:15
Dynamic SQL doesn't exist in Baan 4.. only Baan 5.

What do you mean with that excatly? I use sql.parse, sql.exec... on many occasions in baan 4.

/lakoon

dave_23
24th May 2005, 19:51
Maybe I should rephrase that -

Dynamic SQL exists in Baan 4 - but the standard baan sessions rarely use it.

Dave

lakoon
24th May 2005, 21:39
Hello Dave

o.k. ;-)

/lakoon