Are there components for Microsoft SQL Server?
Yes. In the mssql subdirectory of the jdbc package I’m using MS SqlServer and my adaptor fails with the message “‘CHAINED’ is not a recognized option” Um yes. We’ve got the property the wrong way round! When using MS Server you need to set the UsingChainedTransactions property to true. This will be rectified. Although probably not soon enough for some of our users. There is another strand to this however – if you are trying to take advantage of the polling facility given by the SybaseSource class then it doesn’t matter what your properties file is set to as “SET CHAINED OFF” is hardcoded. So it won’t work at all. Use the more recent MSSqlSource class. Strings larger than 255 characters are truncated when using the Opta driver. You are using the SQL Server 6.5 compatible mode. The SQL Server 6.5 supports only strings with a size up to 255 characters. You are using this mode because JDBC subprotocol is set to inetdae or inetdea6. You need to modify the connection URL to use the JDBC subp
Yes. In the mssql subdirectory of the jdbc package I’m using MS SqlServer and my adaptor fails with the message “‘CHAINED’ is not a recognized option” Um yes. We’ve got the property the wrong way round! When using MS Server you need to set the UsingChainedTransactions property to true. This will be rectified. Although probably not soon enough for some of our users. There is another strand to this however – if you are trying to take advantage of the polling facility given by the SybaseSource class then it doesn’t matter what your properties file is set to as “SET CHAINED OFF” is hardcoded. So it won’t work at all. Use the more recent MSSqlSource class. Strings larger than 255 characters are truncated when using the Opta driver. You are using the SQL Server 6.5 compatible mode. The SQL Server 6.5 supports only strings with a size up to 255 characters. You are using this mode because JDBC subprotocol is set to inetdae or inetdea6. You need to modify the connection URL to use the JDBC subp