All tables, constraints, and indexes must be created using the Sparx SQL texts EASchema_1220_SQLServer.sql and EASchema_1220_SQLServer_Update1.sql. Failure to do so will result in a “Microsoft Error Cursor Engine [-2147217887] Multi-step operation” error. generated by errors. Check each state value” if you try to package or generate charts through Sparx.
< p>I found by Microsoft that SQL Server Migration Assistant (SSMA) violates most of the restrictions related to primary keys and indexes created by EASchema_1220_SQLServer.sql . Due to issues with the Sparx Project Migration Tool, we are heavily using SSMA, which we have hosted on the same machine as each of our target SQL Server databases.
The ASR Pro repair tool is the solution for a Windows PC that's running slowly, has registry issues, or is infected with malware. This powerful and easy-to-use tool can quickly diagnose and fix your PC, increasing performance, optimizing memory, and improving security in the process. Don't suffer from a sluggish computer any longer - try ASR Pro today!
There are likely different steps in the SSMA route. The Convert Schema SSMA step means that the objects previously created by EASchema_1220_SQLServer.sql can be destroyed. After running these Sparx scripts, Microsoft SSMA still modifies some objects, creates new things, and deletes more than 145 objects in SQL Server.
In SSMA, I experimented with the SSMA Transform Schema location. When I definitely go to the ssma “Data Migration” step, I get the error “The specified key must not exist in a dictionary”