Currently, table KYLO_ALERT_CHANGE does not have a primary key set. Please add a primary key so that the schema can properly be migrated to MS-SQL Server.
Using (alert_id, state, change_time) as primary key should be valid: a combination of alert_id, state, change_time should always be unique. change_time is never null, as it is filled in constructor JpaAlertChangeEvent#JpaAlertChangeEvent(com.thinkbiganalytics.alerts.api.Alert.State, java.security.Principal, java.lang.String, java.io.Serializable)
I have created a pull request for this change, please accept it an merge it to the code base: https://github.com/KyloIO/kylo/pull/4