You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Ajoy Bhatia (Jira)" <ji...@apache.org> on 2019/10/26 22:27:00 UTC
[jira] [Commented] (AMQ-4120) SqlServer - SQL Syntax error in
initial table creation
[ https://issues.apache.org/jira/browse/AMQ-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16960444#comment-16960444 ]
Ajoy Bhatia commented on AMQ-4120:
----------------------------------
Surprised that this issue still exists in 5.15.9, even after so many years. As Tim asked, will this affect function or performance? In our case, ActiveMQ takes about 3 to 4 minutes to establish connections during server start-up. Could it be related to this?
> SqlServer - SQL Syntax error in initial table creation
> ------------------------------------------------------
>
> Key: AMQ-4120
> URL: https://issues.apache.org/jira/browse/AMQ-4120
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.7.0
> Environment: Windows Server 2008 R2, 64bit, MS SQL Server 2008 persistence adapter.
> Reporter: Rasitha Wijesinghe
> Priority: Minor
> Fix For: NEEDS_REVIEW
>
>
> When using SQL Server as the backing data store and creating the AMQ tables for the very first time, the following error is logged:
> INFO | jvm 1 | 2012/10/19 11:12:03 | WARN | Could not create JDBC tables; they could already exist. Failure was: ALTER TABLE ACTIVEMQ_ACKS DROP PRIMARY KEY Message: Incorrect syntax near the keyword 'PRIMARY'. SQLState: S1000 Vendor code: 156
> INFO | jvm 1 | 2012/10/19 11:12:03 | WARN | Failure details: Incorrect syntax near the keyword 'PRIMARY'.
> INFO | jvm 1 | 2012/10/19 11:12:03 | java.sql.SQLException: Incorrect syntax near the keyword 'PRIMARY'.
> Since there is no specific adapter for SQL Server it uses the DefaultJDBCAdapter which has getDropAckPKAlterStatementEnd() returning "DROP PRIMARY KEY".
> Not sure if this is an issue with other databases as well.
> (Note: If you already have the tables, this error is still present but only logs a DEBUG entry).
> Does it make sense to add a MSSqlJDBCAdapter that overrides getDropAckPKAlterStatementEnd?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)