Every now and then, I run into an instance where a database for Documentum has changed slightly, preventing an upgrade or even startup. There is nothing wrong with the database itself, just the way the database ownership is configured. There are several reasons why this could happen:
- The database was restored after a crash
- The database was moved to a new server
- A new user was created to own the database
This is all fine and can be done properly. However, sometimes it is not done correctly because people rely too much on Documentum to create and update the security without actually paying attention to what is happening in the background. So here are a few tips in how changes in SQL Server need to be played out.