Encountered this message during a recent migration project - sharing what worked - hadn't seen this solution in the other posts - hope it helps someone.
Migration scenario was less common:
- Bitnami LAMP instance to non-Bitnami Win / IIS / MSSQL
- MS SQL DB required a unique schema name
- Moodledata and DB were large - even with the migration tools out there from MS and others, had to be split up to move w/out timeouts/other issues
Usually am working with LAMP instances, and reading other posts, initially thought the DB or moodledata folder got corrupted during splitting/transfer or I missed permissions somewhere. The DB seemed fine though - auto-numbering to identity conversion looked OK, Moodle DB user assigned to the DB, etc. Was desperate to avoid another data migration round!
- Bitnami LAMP instance to non-Bitnami Win / IIS / MSSQL
- MS SQL DB required a unique schema name
- Moodledata and DB were large - even with the migration tools out there from MS and others, had to be split up to move w/out timeouts/other issues
Usually am working with LAMP instances, and reading other posts, initially thought the DB or moodledata folder got corrupted during splitting/transfer or I missed permissions somewhere. The DB seemed fine though - auto-numbering to identity conversion looked OK, Moodle DB user assigned to the DB, etc. Was desperate to avoid another data migration round!
Solution ended up permission-related - had to give the Moodle DB user ownership of the specific DB schema name in addition to normal DB permissions. Once this was set, everything worked fine. This can be set in SSMS under -> Security -> Users -> Add User (or right-click on Properties for an existing user).
Probably avoidable if using the default MS SQL "dbo" schema name, but could not do that here.
Always sounds quick/easy afterward...
Probably avoidable if using the default MS SQL "dbo" schema name, but could not do that here.
Always sounds quick/easy afterward...