Kathy Barthelt / Tuesday, September 22, 2015 / 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 57378 Rate this article: No rating Kathy BartheltKathy Barthelt Other posts by Kathy Barthelt Contact author Facebook page Twitter Linked In YouTube Website
21Mar2023 Infor LX & BPCS Tip: Ensure Correct Tax Code Usage on AP Invoices with this New Enhancement in LX Tuesday, March 21, 2023 Read more A new enhancement in LX adds the “A/P Invoice Tax Code new system parameter” to the Tax System Parameters, SYS810D. This company level system parameter determines whether Item / Vendor Tax Code is mandatory in the Accounts... Read more
1Mar2023 Infor LX & BPCS Tip: The Top 6 Benefits of CLD Wednesday, March 1, 2023 Read more The Configurable Ledger (CLD) is the central repository for a client’s financial accounting data. Did you know it can do all of the following?... Read more
10Jun2025 Infor LN & Baan Tips & Tricks for EXECUTIVES Tuesday, June 10, 2025 Read more FINANCE: Rebuild History for Account Matching (tfgld1218m000) OPERATIONS: Copy Customized Product Structure to Standard Structure (tipcs2232m000) TECHNOLOGY: Authorization and Security: LN REST APIs Read more