if I was in your shoes I would not use the SCRIPT TO, but instead:
1) generate the SQL Script by myself via JDBC Meta Data
2) optionally parse that SQL Script with JSQLParser and De-Parse it into a MSSQL specific dialect.
In practise, I have done it differently though: the JEDIT editor supports Regex Search and BeanShell expression replacement.
I have had to apply only a few search patterns to turn a H2/Oracle script into MSSQL compliant SQL:
Jedit Regex + BeanShell:
TABLE (\w*)\.\"?(\w*)\"? "TABLE [" + _1.toLowerCase() + "].[" + _2.toLowerCase() + "]"
index (\w*)\.(\w*) "INDEX " + _2.toLowerCase()
ON (\w*)\.\"?(\w*)\"? "ON [" + _1.toLowerCase() + "].[" + _2.toLowerCase() + "]"
(\w*)\.(\w*).NEXTVAL "NEXT VALUE FOR " + _1.toLowerCase() + "." + _2.toLowerCase()
/\*TRANSACT: ([\w\s]*)\*/ _1.toUpperCase()
More rules/search expressions may be needed, depending on your database.
Good luck and best regards