About dbForge DevOps Automation for SQL Server

dbForge DevOps Automation for SQL Server is a powerful solution for automating database development and managing the database lifecycle. This solution provides tools for working with all stages of the DevOps process – development, continuous integration, continuous delivery and operation. 

This bundle includes tools for code completion and formatting, comparing and synchronizing databases, generating database documentation, implementing unit tests, capturing SQL Server events, tracking and analyzing the server performance, source-controlling codes right from the IDE, migrating data between systems and other database management and development purposes. 

Supported Operating System(s):

Windows 7, Windows XP, Windows 8, Windows 10

1 Reviews of dbForge DevOps Automation for SQL Server

Overall rating

5.00 / 5 stars

Filter reviews by:

Sort by: Most Helpful | Most Recent

Showing 1 - 1 of 1 results

Do you use this product?Write a review

February 2020

Brandon from Derivco

Verified Reviewer

Company Size: 1,001-5,000 employees

Industry: Computer Software

Time Used: More than 2 years

Review Source: Capterra



Value for money


Customer support




February 2020

Great solution, and I'm sure it will get even better

We've been using Devart SQL tools for quite a long time and already gotten used to their usability. When we found out that there's Devart DevOps Powershell module, which helps to organize continuous CI using Devart SQL tools, we started to implement our own CI. Eventually, it became clear that some tools only partially meet our requirements, while others fulfill them completely.


Since we are developing a database from scratch (state-based principle), the Schema Compare completely suits us, as it does a great job of creating a database on the server from the script folder. Unit Test also works perfectly.


On the contrary, Data Generator only partially meets our requirements, since it is based on a document that states how much data needs to be generated and for which tables. As our database is actively developing and new tables are constantly appearing, we have to re-save the document all the time. Although, I would prefer it to work "on the fly", without the constant re-saving.