Want to optimize your workflow and maximize usability?

In our blog, “An introduction to 8 ApexSQL tools,” we introduced our Toad World® readers a new member in the Quest® family of database tools, ApexSQL. While ApexSQL has 29 (and growing) DBA and developer tools, we narrowed our focus to 8 tools that we thought would be of interest. This year, we’ll expand on that introduction and provide a helpful accompanying blog series for each. 

Click the arrow to watch a video.

Need to graphically represent dependencies between objects in your database?

As a database developer, if you ever come across a task to graphically represent dependencies between objects in your database, then ApexSQL Analyze is just the right tool for the job. 

How can ApexSQL Analyze help me?

ApexSQL Analyze allows customization and design of the database dependency diagram to improve the visual look and readability of the imported database. It's available to filter out the specific objects, hide unreferenced objects and even delete objects from the diagram.

It provides only a visual representation of the imported database and made changes will not be saved into the database. 

ApexSQL Analyze is ideal for developers who want to see graphical dependencies between objects or just visual representation of objects from one or more databases. It can also identify dependencies that exist in dynamic SQL objects like stored procedures and functions. Dependencies of all object types that are listed in Object Browser can be viewed in ApexSQL Analyze. 

To get the desired look and better database readability, please read the following blogs for more information and a preview of the dependency diagram:

• Microsoft SQL Server historical sample database diagram tour 
• What’s new in ApexSQL Developer: ApexSQL Analyze, graphical dependencies 
• How to customize SQL database dependency diagrams

Please share this post

If you think your colleagues would benefit from this blog, share it now on social media with the buttons located at the top of this blog post. Thanks!