Sage 100

 View Only
  • 1.  FYI... something new with SQL 2016. A new ""featur

    Posted 10-17-2017 13:57
    FYI... something new with SQL 2016. A new ""feature"" for setting a default database size broke something in Sage 100. I was getting an error 42000 Modify File failed error, when creating a copy company (or activating a module in a new company code). Google pointed me to the solution, which involved changing the Model (system) database initial file sizes. I went with 8MB each (changed from the 1024 in the attached pic), and the error went away.


  • 2.  RE: FYI... something new with SQL 2016. A new ""featur

    Posted 10-17-2017 14:06
    Thanks for letting us know.


  • 3.  RE: FYI... something new with SQL 2016. A new ""featur

    Posted 10-18-2017 09:19
    That's weird. My SQL Server 2016 already defaults model to 8MB data and log files (up from 4MB in previous versions).


  • 4.  RE: FYI... something new with SQL 2016. A new ""featur

    Posted 10-18-2017 09:22
    I didn't install SQL, so it may have been something set by the customer IT.