Sage 100

Quick fix, change the database recovery model to Simple.  That recycles log file space without any extra steps.

No need to kick everyone out.  Make the change, then you can shrink the log files down to a reasonable size.  (I usually go with ~500MB).  Do not shrink the database file size... just the log file size.

SQL log files are only useful if you have implemented an advanced backup and recovery strategy.  Otherwise, Simple is fine for most Sage 100 systems.

No need to kick everyone out.  Make the change, then you can shrink the log files down to a reasonable size.  (I usually go with ~500MB).  Do not shrink the database file size... just the log file size.

SQL log files are only useful if you have implemented an advanced backup and recovery strategy.  Otherwise, Simple is fine for most Sage 100 systems.

Quick fix, change the database recovery model to Simple.  That recycles log file space without any extra steps.

Yes, all MAS_* SQL databases can be set to Simple (when you don't have an advanced backup and recovery plan).

No need to kick everyone out.  Make the change, then you can shrink the log files down to a reasonable size.  (I usually go with ~500MB).  Do not shrink the database file size... just the log file size.

SQL log files are only useful if you have implemented an advanced backup and recovery strategy.  Otherwise, Simple is fine for most Sage 100 systems.

Yes, all MAS_* SQL databases can be set to Simple (when you don't have an advanced backup and recovery plan).

No need to kick everyone out.  Make the change, then you can shrink the log files down to a reasonable size.  (I usually go with ~500MB).  Do not shrink the database file size... just the log file size.

SQL log files are only useful if you have implemented an advanced backup and recovery strategy.  Otherwise, Simple is fine for most Sage 100 systems.

Quick fix, change the database recovery model to Simple.  That recycles log file space without any extra steps.

Change the recovery model, then shrink the log file (while setting the new size at the same time).  Repeat for each database. 

Rarely you'll have to repeat, if there is an active transaction in the wrong location within the log, blocking the shrink... Check the file size afterwards to make sure the shrink works.

Note: the new size is not a limit.  SQL will automatically expand the log file size if needed, but it will only do that in times of heavy SQL activity (like running a big "recalculate" utility).  The "Simple" recovery method just means the log space is automatically recycled (only holding actively-being-processed-transactions).

Yes, all MAS_* SQL databases can be set to Simple (when you don't have an advanced backup and recovery plan).

No need to kick everyone out.  Make the change, then you can shrink the log files down to a reasonable size.  (I usually go with ~500MB).  Do not shrink the database file size... just the log file size.

SQL log files are only useful if you have implemented an advanced backup and recovery strategy.  Otherwise, Simple is fine for most Sage 100 systems.

Quick fix, change the database recovery model to Simple.  That recycles log file space without any extra steps.

@Kevin Moyes I ran the utility this evening on three different databases and the utility will not run. The screen would just disappear after I select okay and never started the shrinking process. I would go back in to check the log file size and it's still the same size. What does this mean? (Thank you for the screenshots they were very helpful).

Change the recovery model, then shrink the log file (while setting the new size at the same time).  Repeat for each database. 

Rarely you'll have to repeat, if there is an active transaction in the wrong location within the log, blocking the shrink... Check the file size afterwards to make sure the shrink works.

Note: the new size is not a limit.  SQL will automatically expand the log file size if needed, but it will only do that in times of heavy SQL activity (like running a big "recalculate" utility).  The "Simple" recovery method just means the log space is automatically recycled (only holding actively-being-processed-transactions).

Yes, all MAS_* SQL databases can be set to Simple (when you don't have an advanced backup and recovery plan).

No need to kick everyone out.  Make the change, then you can shrink the log files down to a reasonable size.  (I usually go with ~500MB).  Do not shrink the database file size... just the log file size.

SQL log files are only useful if you have implemented an advanced backup and recovery strategy.  Otherwise, Simple is fine for most Sage 100 systems.

@Kevin Moyes I ran the utility this evening on three different databases and the utility will not run. The screen would just disappear after I select okay and never started the shrinking process. I would go back in to check the log file size and it's still the same size. What does this mean? (Thank you for the screenshots they were very helpful).

Change the recovery model, then shrink the log file (while setting the new size at the same time).  Repeat for each database. 

Rarely you'll have to repeat, if there is an active transaction in the wrong location within the log, blocking the shrink... Check the file size afterwards to make sure the shrink works.

Note: the new size is not a limit.  SQL will automatically expand the log file size if needed, but it will only do that in times of heavy SQL activity (like running a big "recalculate" utility).  The "Simple" recovery method just means the log space is automatically recycled (only holding actively-being-processed-transactions).

Yes, all MAS_* SQL databases can be set to Simple (when you don't have an advanced backup and recovery plan).

No need to kick everyone out.  Make the change, then you can shrink the log files down to a reasonable size.  (I usually go with ~500MB).  Do not shrink the database file size... just the log file size.

SQL log files are only useful if you have implemented an advanced backup and recovery strategy.  Otherwise, Simple is fine for most Sage 100 systems.

@Kevin Moyes I ran the utility this evening on three different databases and the utility will not run. The screen would just disappear after I select okay and never started the shrinking process. I would go back in to check the log file size and it's still the same size. What does this mean? (Thank you for the screenshots they were very helpful).

Change the recovery model, then shrink the log file (while setting the new size at the same time).  Repeat for each database. 

Rarely you'll have to repeat, if there is an active transaction in the wrong location within the log, blocking the shrink... Check the file size afterwards to make sure the shrink works.

Note: the new size is not a limit.  SQL will automatically expand the log file size if needed, but it will only do that in times of heavy SQL activity (like running a big "recalculate" utility).  The "Simple" recovery method just means the log space is automatically recycled (only holding actively-being-processed-transactions).

Yes, all MAS_* SQL databases can be set to Simple (when you don't have an advanced backup and recovery plan).

No need to kick everyone out.  Make the change, then you can shrink the log files down to a reasonable size.  (I usually go with ~500MB).  Do not shrink the database file size... just the log file size.

SQL log files are only useful if you have implemented an advanced backup and recovery strategy.  Otherwise, Simple is fine for most Sage 100 systems.

Quick fix, change the database recovery model to Simple.  That recycles log file space without any extra steps.

No need to kick everyone out.  Make the change, then you can shrink the log files down to a reasonable size.  (I usually go with ~500MB).  Do not shrink the database file size... just the log file size.

SQL log files are only useful if you have implemented an advanced backup and recovery strategy.  Otherwise, Simple is fine for most Sage 100 systems.

Quick fix, change the database recovery model to Simple.  That recycles log file space without any extra steps.

I don't know where I got the attached file detailing how to shrink th e SQL log file.  It may have been someone from 90 Minds.  If so, my apologies for not citing my source of information.

No need to kick everyone out.  Make the change, then you can shrink the log files down to a reasonable size.  (I usually go with ~500MB).  Do not shrink the database file size... just the log file size.

SQL log files are only useful if you have implemented an advanced backup and recovery strategy.  Otherwise, Simple is fine for most Sage 100 systems.