Why does suid change in a database being loaded to match sysdatabases?
During the load of a database, the following error messages may display: Error 3115 Severity 10: User %.*s in database %.*s has suid %d, which is the same as the suid of the DBO (as defined in Sysdatabases). User %.*s will be given suid %d. Error 3116 Severity 10: When all load transactions have been completed for database %.*s, user %.*s should be given a unique suid. These errors occur due to a condition that causes inconsistency in the user information between source and target databases. The load attempts to update sysusers..suid for the target database to match the source suid. However, doing this would cause duplicate suids in sysusers, which is not allowed because there is a uniqueness requirement for suid.
Related Questions
- With project, application and database information loaded into the ITPMS, how do I search for information that will help my agency understand what others have done?
- Does the Teachers Planner need a database program such as Microsoft Access loaded on my computer to enable it to run?
- Can user and historical training records be loaded into my TrainCaster LMS database?
