Hi All,
I'm unable to delete a user from SL 2018. Here's the error...
Thanks.
Hi All,
I'm unable to delete a user from SL 2018. Here's the error...
Thanks.
Excellent suggestion. Thanks again.
I would definitely backup the databases first. Depending on the severity of failure, you could restore the backups to a new name, script out the failing object as "alter", then run the script in the production system (either application or system database.) If all else fails, restore the databases under the original name and move forward.
Good morning Stuart,
From what I could tell in our databases, the customized objects have "x_" prefix in the object name (e.g. x_CustomObject). I don't know if any of the stock objects were edited or modified. I guess I could backup the databases before running the "Execute Master Indexes, Views and Stored Procedures" and restore the system and application databases if we experience failure in testing - which must be extremely thorough. Would you agree?
Thank you very much Stuart.
Good morning, Ed. I'm going to reply to both of your most recent questions. First, it will affect both system and application databases.
My experience has been if the views, indexes, procs are COMPLETELY custom (in other words, they were added to existing "stock" objects) the "Execute Master Indexes, Views and Stored Procedures" process will not affect them.
On the othe hand, if by custom you mean that the stock versions were edited, then the process will overwrite and remove any customizations.
Will running the "Execute Master Indexes, Views and Stored Procedures" in Database Maintenance wipe out all the customized objects (views, stored procs) in the user/application databases? Thanks.
Stuart, yes found it there on the app server under the Administrative Tools.
Do you know if "Execute Master Indexes, Views and Stored Procedures" only updates the system database or does it update the application databases as well? I guess it's best to backup all the databases before running the update.
Thanks again Stuart.
Ed, are you sure it's not on the app server? It would be listed under Windows Administrative Tools.
Stuart, I launched the MS Dynamics SL Database Maintenance (this app does not exist on the app server running Dynamics) and I'm getting the message below...any idea? Thanks.
I will give that a try. Thank you Stuart.
Ed, it looks like you're missing the primary index on the <systemdatabase>.UserRec table. I'd be wondering if there weren't other indexes missing. You could try running the Database Maintenance\Execute Master Indexes, Views and Stored Procedures process.
Martin Dráb
601
Most Valuable Professional
Abhilash Warrier
416
Adis
384
Super User 2025 Season 1