schema compare

Easy ways to quickly exclude objects from schema synchronization

Many users of dbForge Schema Compare for SQL Server ask us how to exclude all the objects or a group of objects at once from synchronization. It is not a problem.

Pay attention to the document with comparison results. In the middle of the grid, just between Source Objects and Target Objects columns, you can see two columns – one with check boxes (they will help you exclude the objects from the synchronization or include them), the other – with operations which will be applied to the Target objects during the synchronization.

Document scomp

Document with comparison results

4 ways to exclude all the objects from the synchronization:


What’s New in dbForge Schema Compare for SQL Server v1.10?

Devart has released today the improved version 1.10 of dbForge Schema Compare for SQL Server, a sophisticated tool specially designed to meet your specific comparison tasks, help analyze schema differences at a glance, and synchronize them correctly, saving time and efforts.

dbForge Schema Compare for SQL Server 1.10 features the following enhancements:


dbForge Schema Compare for MySQL 1.00 to deliver speed, simplicity, and safety!

Dear users,

Devart has released today dbForge Schema Compare for MySQL 1.00 – a special advanced tool for modern comparison and synchronization of MySQL databases. dbForge Schema Compare for MySQL 1.00 meets the needs of both database administrators and developers to automate and simplify the diversity of tasks related to updating and migrating of MySQL databases.

Being part of dbForge Studio for MySQL, a company’s bestseller product for MySQL database administration and development, the functionality of dbForge Schema Compare has met approval of many DBAs and developers.

Speed, simplicity, and safety

As a modern MySQL database management tool, dbForge Schema Compare is based on the solid cornerstones vital for smooth updating and migrating of MySQL databases. They are speed, simplicity, and safety.

The new product provides database administrators and developers with capabilities to quickly compare databases regardless of their structure or MySQL server version. It reduces the intensive hours of schema differences management to minutes and guarantees quick databases synchronization without errors and program misoperation.

dbForge Schema Compare has passed hundreds of usability tests to simplify schema comparison and deliver the clear display of comparison results listing object differences in the grid and showing their DDL differences under the grid. Multiple options for quick sorting, filtering, and search of schema differences ensure easy management.

In modern fast-pace environment safe and error-free schema synchronization is one of key points. dbForge Schema Compare generates a standards-driven synchronization script to guarantee the smooth synchronization. Prior to the script generation, a preview of the synchronization script for every compared schema object is available.

Main product features include:


Coming Soon: dbForge Schema Compare for SQL Server v1.10

After analyzing our users’ feedback on the first release of dbForge Schema Compare for SQL Server. We decided to change our roadmap for this product and to release version 1.1 of the product before adding new major features.

So what new features will this version include?


Synchronization script is too large – what shall I do?

In my previous post Schema Comparison Stress Testing I mentioned problems we met testing dbForge Schema Compare for SQL Server on large database. In this post I would like to give you some tips on processing large synchronization scripts.

Problem Description

Suppose you have compared two databases and want to synchronize them.  You tried to generate the synchronization script but it’s about 100 Mb and simply couldn’t be stored in the memory. When you open it in SQL editor for execution, the application fails with ‘Out Of Memory’ error.


There are two solutions for this problem:


Schema Comparison Stress Testing

A few weeks after the first version of dbForge Schema Compare for SQL Server had been released we received a letter from one of our users who was testing our product to find out if it’s capable to support his DBA tasks. Here is the excerpt from his letter:

Nowadays I work as ERP-system (industry enterprise management system) adoption consultant. Though this ERP-system was originally developed for Microsoft SQL Server 2000 platform but it allows deployment on SQL Server 2005. Second decision has better performance characteristics, but at the same time architectural differences between SQL Server version 2000 and 2005 impede installation of patches and regular database maintenance operations.

The only way out of this situation is this:

  • periodically downgrade database from SQL Server 2005 to 2000
  • perform maintenance operations over database on SQL Server 2000 platform
  • upgrade database back to SQL Server 2005

But this decision makes difficulties…


Synchronizing views between MySQL databases

How to compare and synchronize MySQL views? Recently we discovered some tricks in schema synchronization process of MySQL databases. It’s about how MySQL creates views and tables with foreign keys. I’m going to explain them and give workarounds for dbForge Studio for MySQL users.