Search code examples
sql-serveramazon-web-servicesjdbcaws-sct

Why does AWS Schema Conversion Tool use the JAR format for for MS SQL Server?


During a demo in a recent AWS webinar, a JAR file was specified as a driver for the Schema Conversion Tool to connect to an MS SQL Server db (I am providing a screenshot from the webinar). Why was JDBC chosen? Was this optional, and was a choice made by the person who presented the webinar? If so, what other options would be available as a driver?

enter image description here


Solution

  • From Schema Conversion Tool documentation:

    For the AWS SCT to work correctly, you must install the JDBC drivers for your source and target database engines.