schema compare

Would you like to change data types or other attributes for multi tables in one shot?

Recently we’ve got a letter from a customer asking how to alter all float datatype to double datatype in one “Find and Replace all” shot. Good news! dbForge Studio can do this.  Let’s see how Find and Replace functionality,  Schema Compare tool,  and a database project of dbForge Studio will do their best to change the required properties at a heat.
(more…)

Table data verification for safe schema synchronization

Preserving data in tables after synchronization is one of requirements for successful schema synchronization. dbForge Schema Compare for SQL Server offers two mechanisms of preserving tables data during synchronization, they are warning the users about data loss and restoring data in recreated objects.

But it is not all, dbForge Schema Compare for SQL Server goes on and offers table data verification during synchronization.

How it works

(more…)

Bulletproof database synchronization with dbForge Schema Compare for SQL Server v1.50

Devart, a vendor of native connectivity solutions and development tools for Oracle, SQL Server, MySQL, PostgreSQL, InterBase, Firebird, and SQLite databases, has announced the release of dbForge Schema Compare for SQL Server 1.50, a sophisticated tool specially designed to meet a diversity of comparison tasks, help analyze schema differences at a glance, and synchronize them correctly, saving time and efforts.

With the new release, Devart continues its dedication to providing a line of safe as well as powerful tools for SQL Server database synchronization.

The highlights of Schema Compare for SQL Server 1.50 include:

(more…)

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. (more…)

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:

(more…)

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

Dear users,

Devart has released today dbForge Schema Compare for MySQL – 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.

(more…)

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?

(more…)

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.

Solution

There are two solutions for this problem:

(more…)

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…

(more…)