on 01-27-2015 4:39 PM
Is there a recommended maximum size an E table can have in a BPC application? One of our application E table is almost 70M records. I am exploring archiving some of the data. Wondering what the impact would be if the size grew to 100M records.
There is no maximum recommended size of E table. Each DB has it's own max size and usually it's measured in TB, not in number of records.
Again, 70M records those days is not such a big table, but it depends what DB you are using and on what hardware it runs. In any case, if you can archive half of the records you should see performance improvement.
To have a better idea you can turn on statistics and check how much time you "read & write" are taking. This can give you an indication of how much time you'll save and if it's inline with your customers' expectations or not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
14 | |
4 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.