[ https://issues.jboss.org/browse/TEIID-3376?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-3376 at 3/16/15 7:29 PM: ---------------------------------------------------------------- Added another commit to fix an issue with the SQL Server start method. We are now defaulting the database version to an exception if not set so that the behavior is more clear. With the old logic the translator would start with the default version and not see that the time type was available, then once it initialized the capabilities would see that the time type was available and the scenario from this issue would fail. Also added a minor of synchronization around modifications to the executionfactory state to ensure consistency. Although there may need to be some additional locking on the the other executionfactory method calls to ensure full consistency. was (Author: shawkins): Added another commit to fix an issue with the SQL Server start method. We are now defaulting the database version to an exception if not set so that the behavior is more clear. With the old logic the translator would start with the default version and not see that the time type was available, then once it initialized the capabilities would see that the time type was available and the scenario from this issue would fail. Also added a minor of synchronization around modifications to the executionfactory state to ensure consistency. -- This message was sent by Atlassian JIRA (v6.3.11#6341)