Data compress in 5.0 SP 1 for item ledger entry or value e.

vanrofivanrofi Member Posts: 272
Hi All,

As the database grows, we feel the need to compress the data. In older versions I remember that compressing Item LE or Value entries was possible. However I cannot find this in 5.0. I see the data compression tools but none of the reports available handle ILE or VE.

](*,)

Many thanks again for your help

Comments

  • bbrownbbrown Member Posts: 3,268
    What is driving this "feeling"? How large is the database? How large are these tables?
    There are no bugs - only undocumented features.
  • vanrofivanrofi Member Posts: 272
    Database Size is 88gb

    ILE for all companies in the DB is approx 2gb
    VE for all companies is approx 12gb
  • bbrownbbrown Member Posts: 3,268
    What are you trying to accomplish? 88 GB is not a large database and I don't see a reason to be considering data compression.
    There are no bugs - only undocumented features.
  • vanrofivanrofi Member Posts: 272
    Is there no Limit per License?
    With the license we run 4 databases...I gave you the figures of the largest db, so I think you can multiply with 2 or 2,5.

    Anyway, it does not hurt to keep the database lean, why does std. navision foresee compression in old versions and in new version for all other ledgers, without questioning the largeness of the db?

    Thx anyway for your remark, but I'm still curious why this feature has vanished?
  • kinekine Member Posts: 12,562
    The function is there from times when most users were using Native DB server, which have size limits...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • vanrofivanrofi Member Posts: 272
    So you confirm that the function isn't there anymore and that there is no size limit on license?
  • David_SingletonDavid_Singleton Member Posts: 5,479
    vanrofi wrote:
    So you confirm that the function isn't there anymore and that there is no size limit on license?

    The size limit on database was removed about 10 years ago. I am sure the majority of Navision users don't even know what it it.
    David Singleton
  • vanrofivanrofi Member Posts: 272
    Oh, we have in our license the granule 1370 : Database expansion per Gb...it must be less than 10 years...
    The Native databases were also limited to a certain size, like 128 gb or something?

    Anyway, that was not even part if the initial question, we are on sql since few months, so no worry about that.

    Still I feel that a cleanup of thes value entries and ILE are a must after a while: there are millions of records in it.
  • David_SingletonDavid_Singleton Member Posts: 5,479
    vanrofi wrote:
    Oh, we have in our license the granule 1370 : Database expansion per Gb...it must be less than 10 years...
    The Native databases were also limited to a certain size, like 128 gb or something?

    Anyway, that was not even part if the initial question, we are on sql since few months, so no worry about that.

    Still I feel that a cleanup of thes value entries and ILE are a must after a while: there are millions of records in it.

    Well one other thing to rememebr; those compressiion routines will most likely destroy your data. If you have any modifications to your system (and who doesn't) I have never seen ever a case where the compression routines were updated to match. So the compression may cause you a lot of problems.

    I have done a couple of jobs where I have had t some in and "Uncompress entries" to make the system stable again.

    So this might be part of the reason why the routines are gone.
    David Singleton
  • vanrofivanrofi Member Posts: 272
    So better invest in SQL tuning so that millions of records don't matter?

    OK, I'm not stubborn, If the specialists say no, i won't take any risks.

    >Thx!
  • krikikriki Member, Moderator Posts: 9,110
    vanrofi wrote:
    So better invest in SQL tuning so that millions of records don't matter?
    Definitely!
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!


Sign In or Register to comment.