DB syncs, except for QUOTED_IDENTIFIER

Discussion of open issues, suggestions and bugs regarding database management and development tools for SQL Server
Post Reply
dental0
Posts: 1
Joined: Mon 06 Oct 2014 20:55

DB syncs, except for QUOTED_IDENTIFIER

Post by dental0 » Mon 06 Oct 2014 21:21

I am using dbForge Schema Compare v3.8.252, with SQL Server 2012 Service Pack 1

It never completely syncs my databases. Every time I update the test database, and try to push the changes to prod, they go but then after refreshing the comparison, all modified stored procs show as different. The part that is different can be:

SET QUOTED_IDENTIFIER OFF
GO

or

SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS OFF
GO

or even a BLANK line at the end of the stored proc. It is very annoying. And frankly, I don't care about this QUOTED_IDENTIFIER option. I just want my data to sync like it used to do, with previous versions of the software (which I used on previous versions of MSSQL).

Am I missing a syncing option? Thanks!

alexa

Re: DB syncs, except for QUOTED_IDENTIFIER

Post by alexa » Tue 07 Oct 2014 12:03

Could you please provide us the following information:

1. CREATE definitions of the compared Source and Target objects.
2. Screenshots of dbForge displaying the differences?
3. Values of QUOTE_IDENTIFIER and ANSI_NULLS of the compared Source and Target databases.
4. Generated *.scomp schema comparison document.

You can send a reply straight to our support system at supportATdevartDOTcom, so we will keep further correspondence with you on this issue via e-mail.

alexa

Re: DB syncs, except for QUOTED_IDENTIFIER

Post by alexa » Tue 14 Oct 2014 11:49

We were able to reproduce this issue and will fix it in one of the next product builds. We will notify you once it's available for downloading.

In the meanwhile, we suggest you to select the 'Ignore QUOTED_IDENTIFIER and ANSI_NULLS' option on the 'Options' page of the schema comparison wizard in order to ignore QUOTED_IDENTIFIER.

alexa

Re: DB syncs, except for QUOTED_IDENTIFIER

Post by alexa » Tue 20 Sep 2016 16:32

We would like to let you know that we have released dbForge Schema Compare for SQL Server, v4.2 where the issue you reported is fixed https://www.devart.com/dbforge/sql/sche ... nload.html

Thank you for your help in improving dbForge Schema Compare for SQL Server.

Post Reply