Delete User Error

(0) Share

Report

Posted on by Ed-DBA

100

Hi All,

I'm unable to delete a user from SL 2018. Here's the error...

Thanks.

I have the same question (0)

All responses (10)

Answers (1)

Community Member on at

Like (1)

Report

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.

Was this reply helpful? Yes No
Ed-DBA 100 on at

Like (0)

Report

I will give that a try. Thank you Stuart.

Was this reply helpful? Yes No
Ed-DBA 100 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

Ed, are you sure it's not on the app server? It would be listed under Windows Administrative Tools.

Was this reply helpful? Yes No
Ed-DBA 100 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Ed-DBA 100 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Ed-DBA 100 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Verified answer

Ed-DBA 100 on at

Like (0)

Report

Excellent suggestion. Thanks again.

Was this reply helpful? Yes No