Ryan V.
"SQL is not Complete without SQL Complete"
What do you like best about dbForge SQL Complete?
SQL Complete has become a mandatory part of our IDE. It is not simply an "add-on" but a necessary tool expanding the flexibility of SSMS in essential ways. By allowing the creation of code templates for repetitive code writing known as "snippets", we have been able to reduce the time required to write code and ensure more consistent code structure across our platform. This also reduces the number of coding errors in everything from writing new scripts using snippets, to writing ad-hoc CRUD actions since SQL Complete fills in much of what is needed for you. SQL Complete really shines when needing to navigate to object definitions or scripting out records from one environment (client / production) to another (test / dev). What do we like best about SQL Complete? All of it. What do we not like...environments where SQL Complete is not loaded. Once you have it, you will find yourself missing it where it does not exist. Review collected by and hosted on G2.com.
What do you dislike about dbForge SQL Complete?
The update process still feels a bit finicky when I have Visual Studio open, being that it does not like to update (I have to close everything). I also have found the variables in snippets seem to give trouble when I have multiple variables on the same line of code (it will tab to the wrong location). These are nitpicks at best. Review collected by and hosted on G2.com.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through a business email account
Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.