Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Data Sizing Moving to LN

The Infor LN database must be created with the appropriate size. For example, if at least 150 GB is required for a year, create the database with the required size from the beginning. Do not let the size increase to the required size and cause additional fragmentation in the database and the NTFS volume.  Set the autogrowth to a minimum of 10 percent or 1 GB (for each extent) to avoid fragmentation on file system level. Never use the default extent size of 1 MB.

Previous Article BPCS/LX Tip of the Week: Work Center & Machine Locations
Next Article BPCS/LX TIP OF THE DAY: MATERIAL REQUIREMENT DATES AND LEAD TIME OFFSETS IN MRP
Print
118765 Rate this article:
No rating

Contact

Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

For many manufacturers, ERP has been the foundation of their business for years. It manages orders, inventory, production, purchasing, and financials. But as technology and business demands continue to evolve, many organizations are beginning to ask a different question:

Is our ERP environment ready for what's next?

For some, that conversation includes cloud migration. For others, it's about integration, visibility, analytics, or supporting future growth.

The good news is that modernization doesn't have to start with a major migration project.

Start with the Business, Not the Technology

One of the biggest misconceptions about modernization is that it begins with selecting a new platform.

In reality, the most successful projects begin by understanding the business challenges you're trying to solve.

Questions worth asking include:

Categories