- Newest
- Most votes
- Most comments
It's possible that the differences in the errors you're seeing between the source and target databases are related to differences in the database engines or versions. Even though SQL Server and RDS SQL Server are similar, there can still be slight differences in syntax or features that could cause errors during migration.
I would recommend investigating each error individually to determine the cause and whether it can be safely ignored. In some cases, the errors may be related to differences in collation, data types, or other settings between the source and target databases.
AWS Schema Conversion Tool (SCT) can help you identify and resolve issues related to database migration. You can use SCT to assess and convert your databases to the target format, and it can also provide recommendations for resolving issues and errors that are detected during the migration process.
I would also recommend testing the migrated databases thoroughly to ensure that all data and functionality has been successfully transferred to the new environment.
Relevant content
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Thanks Hash,
I have created the database in RDS and 90% of the syntax was removed but one or two errors were there (XML datatypes) but, where I did the assessments for SQL server everything was in green(100% auto-converted) but here I can see the errors. why this error or warning did not come in the assessment report?
Please share if you have any datatypes which are not supported in was rds SQL server from SQL server.