Consequential Solutions Ltd

PRODUCTS – SQL Performance Report

SQLPRep 2015 aka SQL Performance Report is our newest software product that takes any TSQL and produces a concise, readable, highlighted performance report allowing you to greatly reduce your time spent in developing, debugging, optimising, testing and reviewing TSQL.

DOWNLOAD OUR FREE LITE SOFTWARE HERE

Try out the LITE version of SQLPRep by either downloading the self-extracting archive using the password “ConsequentialSolutions” or downloading the zip file using the same password.

No installation is required but the LITE version requires internet access to activate. We’d love any feedback so please send us your thoughts via our contact page.

Sign up to our mailing list to the right or follow us on twitter for current updates and important news.

SQLPRep SQL performance report image

An overview of some of the features of SQL Performance Report, including highlighting problem areas, data comparison, schema exploration and comparison.

OUR APPROACH TO OPTIMIZATION

You prepare your test data, run it through SQLPRep and you have a single sql performance report that is easy to read, has all the information grouped together that you need and all the detail there that can be printed out and taken to the room of your choice, where you can simply highlight the many problems that will now be obvious at a glance.
Taking things a step further with our expert training you will be able to pick out almost all causes of badly performing TSQL and have a library of techniques to resolve them. If you are really unlucky and have that rare, never before tried issue, then we are here to help you resolve it with a solution provided by our crack team.

COMMUNITY

At Consequential Solutions we think its important to support users with helpful SQL performance and optimisation information, links, scripts, software, training, consulting, challenges and puzzles to expand applications of SQL. With our SQL blog we hope to go some way towards making what we have developed accessible and adding a bit of fun to the SQL community.

We use Cookies - By using this site or closing this you agree to our Cookies policy.
Accept Cookies
x