The latest beta version of Redgate Sql Compare, version 8, has sparked discussion among database professionals. As a long-time user of SQL Compare 6, I decided to test the beta and share my initial experiences. This review focuses on the key changes and whether they represent an improvement over previous versions, particularly for users accustomed to the workflow of SQL Compare 6.
One of the first noticeable changes is the redesigned project wizard. While aiming for efficiency, it opens with the most recently used project, which isn’t always ideal. The previous project is not readily accessible within the wizard, forcing users to cancel and manually open a different project. For someone like myself, who manages around 30 projects differentiated mainly by database, this filename-centric approach in SQL Compare 8 feels less intuitive than SQL Compare 6’s method. In version 6, project selection felt directly tied to the database server being updated, streamlining the process significantly. The absence of column sorting and the project menu defaulting to “My Documents” further complicates project retrieval, often leading to frustration and a return to the familiar SQL Compare 6.
Another point of contention is the removal of the “Switch synchronization direction” feature. This was a handy shortcut in SQL Compare 6 for quickly reversing the synchronization direction. Now, achieving the same action requires navigating back to the wizard and re-synchronizing both databases, adding unnecessary steps to a previously simple task.
However, not all feedback is negative. The new object filter in Redgate SQL Compare 8 is a powerful addition. Although setting conditions can be a bit intricate initially, it offers granular control over object selection for comparison and synchronization. While the complexity might require a learning curve, the filtering capability itself is a welcome enhancement. To improve usability, incorporating preset conditions based on right-click actions on objects, such as “Object Name = [selected object]” or “Object Name <> [selected object],” would greatly simplify common filtering tasks.
Despite the improved filter, the visual cues for object types have become less distinct. SQL Compare 6 used icons effectively within the Filter Objects dialog, allowing for quick visual identification. In version 8, with objects sorted and lacking distinct icons, users must now rely on reading text labels, slowing down object identification, especially for those accustomed to the icon-based system. Furthermore, the clear distinction between SQL 2000 and SQL 2005 objects in SQL Compare 6 was beneficial for managing schema and role differences when synchronizing across different SQL Server versions. This distinction seems less pronounced in the beta, potentially adding complexity when dealing with cross-version database comparisons.
In conclusion, based on my experience with the beta version, Redgate SQL Compare 8 presents a mixed bag of changes. While the enhanced filtering is a positive step, the alterations to project management, synchronization direction switching, and object identification workflow detract from the user experience, at least for users transitioning from SQL Compare 6. Currently, the advantages of SQL Compare 8 beta do not outweigh the efficiency and user-friendliness of SQL Compare 6, making an immediate upgrade seem unlikely for users with similar workflows and preferences.
