dbForge 4.3.85 Synchronization Failure on Drop Constraint

Discussion of open issues, suggestions and bugs regarding database management and development tools for SQL Server
Post Reply
DanielHiebert
Posts: 5
Joined: Tue 08 May 2018 20:13

dbForge 4.3.85 Synchronization Failure on Drop Constraint

Post by DanielHiebert » Tue 08 May 2018 20:21

In our production server using dbForge 4.3.85, I am receiving a synchronization failure syncing two MS SQL databases. This background job had been running every 15 minutes for several days before it began to fail.

A snippet from the log file:
------ Synchronization started: Source: ODS_REITER, Target: ODS_REITER ------
Start Transaction
Error for 'dbo.STLMT_DSACOMMISSIONRANCHES': Incorrect syntax near the keyword 'IF'.


The MS SQL generated by dbForge is as given below. Does anyone have a pointer on where to look for a resolution?

--
-- Dropping constraints from dbo.STLMT_DSACOMMISSIONRANCHES
--
ALTER TABLE dbo.STLMT_DSACOMMISSIONRANCHES
DROP CONSTRAINT IF EXISTS FK_STLMT_DSACOMMISSIONRANCHES_DSACOMMISSIONID
GO

Msg 156, Level 15, State 1, Line 17
Incorrect syntax near the keyword 'IF'.

alexa

Re: dbForge 4.3.85 Synchronization Failure on Drop Constraint

Post by alexa » Thu 10 May 2018 14:48

We will investigate this issue and will answer you as soon as possible.

alexa

Re: dbForge 4.3.85 Synchronization Failure on Drop Constraint

Post by alexa » Thu 10 May 2018 15:45

Could you please provide us the script?

You can send a reply straight to our support system at alexaATdevartDOTcom and supportATdevartDOTcom .

DanielHiebert
Posts: 5
Joined: Tue 08 May 2018 20:13

Re: dbForge 4.3.85 Synchronization Failure on Drop Constraint

Post by DanielHiebert » Thu 10 May 2018 18:38

The script has been sent directly via email. Look forward to your reply.

alexa

Re: dbForge 4.3.85 Synchronization Failure on Drop Constraint

Post by alexa » Fri 11 May 2018 08:44

Thank you for the reply.

From the documentation, it follows that functionality was implemented starting from SQL Server 2016 https://blogs.msdn.microsoft.com/sqlser ... rver-2016/

So, to resolve this issue, you would need to upgrade SQL Server server.

DanielHiebert
Posts: 5
Joined: Tue 08 May 2018 20:13

Re: dbForge 4.3.85 Synchronization Failure on Drop Constraint

Post by DanielHiebert » Wed 23 May 2018 19:52

We are unable to upgrade the SQL Server due to the Cognos software that needs to access it. This issue never occurred when dbForge was run from a development server even though the source and target SQL servers remained the same. When we de-installed dbForge on one server and installed the synchronization on the new server, now this issue appears. From May 11 through May 21st, 2018, the synchronization occurred successfully. Without any change, now since May 22nd, 2108, the synchronization fails consistently due to the script statement.

What causes this intermittent behavior? Is there a work around in dbForge to skip the alter statement that it is generating? The target database is a reporting database; therefore, I am only interested in getting the data replicated to it.

DanielHiebert
Posts: 5
Joined: Tue 08 May 2018 20:13

Re: dbForge 4.3.85 Synchronization Failure on Drop Constraint

Post by DanielHiebert » Wed 23 May 2018 22:43

I would like to point out that if our DBA Team runs the synchronization manually using dbForge, then the issue goes away for a few days. In this case, the DBA team ran the dbForge synchronization manually and it is synchronizing again for the last 2 hours. I'm sure that it will stop at some future time again.

DanielHiebert
Posts: 5
Joined: Tue 08 May 2018 20:13

Re: dbForge 4.3.85 Synchronization Failure on Drop Constraint

Post by DanielHiebert » Wed 30 May 2018 23:53

Please can I have an update on this production issue?

alexa

Re: dbForge 4.3.85 Synchronization Failure on Drop Constraint

Post by alexa » Thu 31 May 2018 16:04

Sorry for the delay on this.

We will fix this issue in the next product build and will notify you once it's available for downloading.

Post Reply