Database development is not limited to an initial copy of a database. On your road you meet multiple enhancements, refactoring, upgrade and many other cases that require changes in a database structure. One of most common cases is to upload database objects from one schema to several schemas. Here the simplicity ends and you are stuck with the questing ‘How to do this?’
Upload manually or automatically?
Devart today releases dbForge Studio for MySQL, v4.50 – cutting-edge administration tool and development environment for professional working with MySQL databases.
With dbForge Studio, Devart continues its initiative to produce efficient database experiences for all the people in MySQL world.
New features in dbForge Studio for MySQL, v4.50 include:
Many-to-many relationships between tables are accommodated in databases by means of junction tables. A junction table contains the primary key columns of the two tables you want to relate.
To create a many-to-many relationship between tables in dbForge Studio for MySQL:
Devart development team is glad to present dbForge Query Builder for SQL Server, a modern and affordable tool that will bring you confidence in creating queries of any complexity. With dbForge Query Builder, Devart continues its initiative to produce efficient database experiences for all the people in SQL Server world.
dbForge Query Builder for SQL Server
Designed specifically for people who are working with databases, dbForge Query Builder blends rich functionality and a simple user interface to provide:
We compared some best-of-breed data comparison tools with dbForge Data Compare 2.00 to find out which one is speedier to compare and synchronize data in SQL Server databases.
The participant tools were tested with default settings on live databases on SQL Server 2008 that installed with default settings on a desktop (with a dual-core processor and 2Gb of RAM). Both the SQL Server and the tools were installed on the same desktop.
Live Databases:
Two databases with total size of 1Gb: 115 tables containing one with 3 million records of numeric and string data types, the other with middle size BLOB data.
Task №1: We measured the speed of each tool while comparing the data, generating an update script, and at last synchronizing the databases.
Data Comparison/Synchronization Performance
Result №1: Tests results show that dbForge Data Compare for SQL Server v2.00 has leaved the competitors far behind.
Task №2: We decided to compare the performance of the selected participant tools based on the main industry-leading competitor’ performance. Besides we took into account the product price and tried to calculate the efficiency as best performance for less money.
Performance/Price
Result №2: This graph shows that not all the tools can be proud of delivering an expected combination of best performance and best price. dbForge Data Compare handles this task well.
Check Shot
To fully complete our research, we decided to go the whole hog and use the aforementioned tools to compare large databases with the size of 120Gb (some tables in these databases have 2.4 billion records, some tables contain 1.5Gb of LOB data, the FILESTREAM table is with 5.3Gb of records). dbForge Data Compare was good at comparison, while neither of the competitive tools compared tables with LOB data and records in the FILESTREAM table. When we excluded such tables, only one tool coped with 2.4 billion records.
Speed rate of dbForge Data Compare is several times higher than other popular competitive tools have.
Try dbForge Data Compare on your database. Delivering qualitative data comparison and synchronization is our fame.
We guarantee quick support and product improvement if dbForge Data Compare fails to compare and synchronize your database. We even may give you the product license for free.
We compared some best-of-breed comparison tools with dbForge Data Compare 2.00 to find out which one is speedier to compare and synchronize data in SQL Server databases.
The participant tools were tested with default settings on live databases on SQL Server 2008 that installed with default settings on a desktop with a dual-core processor and 2Gb of RAM. Both the SQL Server and the tools were installed on the same desktop.
Devart announced the release of a new version of the professional tool for SQL server data comparison and synchronization – dbForge Data Compare 2.00. Committed to support the needs of database-dealing professionals, Devart now delivers a performance-leading SQL comparison tool that incorporates three times faster data comparison and synchronization, the smallest price and greater satisfaction than all other data comparison tools offer.
Incorporating these three components, dbForge Data Compare 2.00 guarantees greater satisfaction and smother database-dealing experience for any SQL comparison and synchronization goals.
The highlights of dbForge Data Compare 2.00 include:
Recently we’ve received a question from one of our customers asking how to synchronize data between companies servers and a data warehouse server. Let’s see how easy it can be done with the help of dbForge Data Compare for SQL Server, a professional tool for data comparison and synchronization.
What we have:
We have two companies ( they use ERP software), each having their own SQL Server database with one table. The companies tables with their customers’ data are saved in the data warehouse as follows:
What we need:
We need to create a data warehouse with all information stored in one set of SQL tables. For example, the created data warehouse should contain a Customer table that contains all records of Company1$Customer and Company2$Customer. This table should contain an extra field with a company name to make the records unique. We need to synchronize only changed records.
How to complete the task:
Data comparison is a difficult and resource-intensive process. For convenience, this process can be divided into several steps.
First, you should compare tables from one database on one server with the database on the other server. You should choose columns for data comparison, and also choose a column that will be a comparison key.
The next step is to choose all data from these tables or some specified part of the data.
The third and the most important step is comparison of the two tables by the selected comparison key itself. During this process the status of each record is set to “only in source”, “only in target”, “different”, or “equal”.
The final steps of the data comparison process are including records to the synchronization and synchronization itself. During these steps records needed for synchronization are chosen, update script is created, and after that the script is executed.
You can read a detailed description of the comparison process here.
Now let’s look at the third step (data comparison) thoroughly.
There are several ways of data comparison that differ only by the side where data comparison is going to be performed – on the server side or on the client PC.
The most important characteristic of any software is its quality. The quality, according to the model specified in the ISO 9126 standard, consists of the following characteristics:
Of course users are not concerned about any quality models and just tell us their suggestions and wishes. It’s these suggestions and wishes that are the most preferred description of any quality characteristic.
Schema Compare for SQL Server 2.00 compares schema snapshots, database backups, and database changes in version control systems to accelerate the work of advanced database developers.
Devart today announced the public availability of Schema Compare for SQL Server 2.00 that delivers new capabilities to help customers more effectively compare databases and more quickly migrate schema changes across different SQL Server versions.
Featuring new functionality, the tool is better equipped to span a full spectrum of database comparison and synchronization tasks and allows completing them at a professional level.
The highlights of Schema Compare for SQL Server 2.00 include: