How many times have you performed an upgrade just to realize with the first posting that some stored procedure is missing or did not -- for some misterious reason -- get created, yet the upgrade completed with no errors? This is especially true when upgrading from several versions aback, when the upgrade path is not too clear, or you have forgotten to apply that critical service pack that would avoided some of the missing objects issues you are now experiencing.
I recently came across a user who wanted to recreate all SmartList Builder
objects because they suspected something was wrong with the installation, however, they did not want to have to use the backend to recreate all the stored procs used by SLB, because of the "fair of missing something or endup damaging something else
"... you know what they say... the client is always right! (not always, but that's the topic of another article).
After scratching my head for a few moments, the answer came in the form of the new Microsoft Dynamics GP Database Maintenance Utility
, but first some history...
Before there was the SQL Maintenance
utility, back in the old days, the former Great Plains Software provided reams of text files…