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 57214 Rate this article: No rating Kathy BartheltKathy Barthelt Other posts by Kathy Barthelt Contact author Facebook page Twitter Linked In YouTube Website
14Jan2025 Infor LX/BPCS Tips & Tricks for EXECUTIVES Tuesday, January 14, 2025 Read more Technology: Reset Purchase Order In Use - Operations: Retain Lot Status on Shipped Resupply Orders - Finance: Inventory Period Balance Freeze - Read more
10Dec2024 Infor LX/BPCS Tips & Tricks: Infor's Product Lifecycle Policy Tuesday, December 10, 2024 Read more Are you up to speed on Infor’s Product Lifecycle Policy for your version of BPCS/LX? Review this document from Infor, and contact Frank Petrasio at Crossroads RMC with any questions about how this may impact your organization. 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