The Tool of Choice for DBAs and Developers
Use Cases and Deployment Scope
The well-known features of [dbForge Studio for SQL Server] not only sell [itself] but serve [to] make a real difference in small shops as the tool is all-encompassing. [When using dbForge Studio for SQL Server,] Teams, such as ours, don't have to acquire additional tools, be it schema comparison and deployment, code completion during coding projects, highly intelligent IntelliSense when it comes to object name lookup, aliasing, [or] code completions/suggestion, and this is just scratching the surface.
Pros
- Schema compare and synchronization
- Database documentation
- Database performance analysis [and] optimization
- On the fly code completion and object identification
- Second to none object export mechanism and supported-formats
Cons
- [The] installation error I've already reported (ABARTN).xml [could use some improvement]. This has to do with Windows Defender (the default Windows anti-virus) not allowing the installation on the default installation directory of dbForge Studio [for SQL Server], thus the error. [With] the workaround, [I] was to disable the anti-virus for the duration of the installation, then turn it back on when the installation [was] been completed.
- [I would like to see] better defined licensing models for larger teams (seated vs. name licenses).
Likelihood to Recommend
No tool on the market is equal to it - be it in its intelligent design, ease of use, ease of integration, multi-platform support, highly engineered features, and much more.
