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

Question

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?

Ilya Berdichevsky · Accepted Answer · 2019-02-27T19:42:10.063

1

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.

edited Feb 27 '19 at 19:42

answered Feb 27 '19 at 19:38

Ilya Berdichevsky

1,249
10
24

Yes I saw that link, but are you certain that JDBC is the only option? Thank you. – Sabuncu Feb 27 '19 at 19:40
As per AWS doc, yes. – Ilya Berdichevsky Feb 27 '19 at 19:42
The tool is (supposedly) written in Java, hence the need of JDBC drivers – NitinSingh May 15 '19 at 07:13

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

1 Answers1