thanks for replying, but I think that is more for better performance point of view, can u imagine if one database contains a lot of companies and a every company keeps their long long retention day ?
Standard Navision gives you date compression. There are some reports to delete e.g. sales orders that have been shipped and invoiced completely and so on.
But the best would be to create some extra tables in which you can move old records of the tables. e.g. sales shipments+its lines+its dimensions. In this way you remove some records from those tables and put them in others improving performance a little for that table but not loosing info. With Navigate you can still find the info if you program it.
For doing this with the different entry tables, is more risky. You should study the date compression to see which records it takes to compress and then move only those (remember there are a lot of other tables involved in these (for Item Ledger Entry:Value entries, dimensions,T6507,...).
Regards,Alain Krikilion No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
I've always been scared of date compression, purely because you lose a lot of the historical detail.
If you do need to do it I would recomend keeping a copy of the database before the compression that you can use to look at the history. Put it on a spare/test server so it's available.
Julian Harper
IT Manager
Laytons Wine Merchants Ltd
I have a huge DataBase.
About 40% of data are on Tab32 & 5802 (due to an Addon we actually use for POS).
If these tables are compressed using DAY as period, nothing is lost... I'm wrong?
You lose the individual info of each entry.
Making a copy for archiving/historical detail purposes would be a good idea.
You might also check how many indexes there are in T32 and check out in the programs if they are really used. If not, you can disable them. Also this will decrease the size of the table.
Regards,Alain Krikilion No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Comments
RIS Plus, LLC
But the best would be to create some extra tables in which you can move old records of the tables. e.g. sales shipments+its lines+its dimensions. In this way you remove some records from those tables and put them in others improving performance a little for that table but not loosing info. With Navigate you can still find the info if you program it.
For doing this with the different entry tables, is more risky. You should study the date compression to see which records it takes to compress and then move only those (remember there are a lot of other tables involved in these (for Item Ledger Entry:Value entries, dimensions,T6507,...).
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
If you do need to do it I would recomend keeping a copy of the database before the compression that you can use to look at the history. Put it on a spare/test server so it's available.
IT Manager
Laytons Wine Merchants Ltd
About 40% of data are on Tab32 & 5802 (due to an Addon we actually use for POS).
If these tables are compressed using DAY as period, nothing is lost... I'm wrong?
Email: mehdi.chahed@dufry.com.tn
DUFRY TUNISIA
Making a copy for archiving/historical detail purposes would be a good idea.
You might also check how many indexes there are in T32 and check out in the programs if they are really used. If not, you can disable them. Also this will decrease the size of the table.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!