Introducing Sql Caddy

Hello all,
Looking for feedback on our new product, Sql Caddy, a tool intended to help enterprise and consulting application support, development and power users with database information to improve query development.

Please take a look at and let us know what you think.

Thank you.
Tom @ Sql Caddy

I believe you may have edited the post to insert the hyperlink, thank you! Now there is a typo at the beginning. Can you remove the Service? I tried but then it wants me to remove the link and I’d rather keep it. :slight_smile:

Thanks again!

I meant “S” not Service.

Seems like it would be useful if I were using sql more right now.

Your sales page has a lot of features on it. What are the problems it solves? Why did you build it? What are the benefits of using sqlcaddy over… nothing/phpmyadmin/etc? Who needs it the most? only data engineers, analysts, engineers, data scientists, or someone else?

Thanks for the feedback, I also feel like we are heavy on features and need to better state the benefits. We are trying to reduce the amount of time spent sifting through databases and sql scripts to write queries. We built it based on experience of having to do just that. Anyone who writes many queries or has to discover the relationships, fields and tables in databases consistently would benefit from this application.

Thanks again. We will continue to try to improve our message. It has been a challenge to try to explain.

1 Like

Don’t want to discourage you, but you are in a crowded market.

Many moons ago we released similar product:

It got us where we are now but I wouldn’t say it is a runway success in terms of sales.

Unless it solves a real pain point(s) - there are too many alternatives, so no one is actively looking for a replacement.

1 Like

Anyone who writes many queries or has to discover the relationships, fields and tables in databases consistently

I doubt anyone describes their work as “I write queries”.

I believe your wording should be updated to speak the way your target users talk - not “write a query”, but “find a record/user/offer/… in database”, and so on.

Your site currently describes how to do something, but not what a prospect would be doing (better).

Maximus - Thank you for the feedback. I agree, there are a lot of tools similar to yours and that would be a difficult market to break into. I may not be looking hard enough, but does your product or any of the others locate relationships based on the sql queries or are they strictly based on foreign key constraints? Our application is intended to help with databases that have less than perfect schema. To uncover domain knowledge automatically from query code instead of the database design. We are also targeting business power users, application support or consultants that have to reverse engineer unknown databases, again with less than perfect design. Where the other tools appear to target database professionals?

rfctr - Thank you for the feedback. Those that we are trying to target do write queries often, but it obviously wouldn’t be their entire job. Maybe we can come up with more broad descriptions of their job that includes writing queries.

All - We are working on a better message that describes the problem more than the features. Still not there yet, but here are some more thoughts…

Problem to solve - Time spent acquiring information and knowledge of unknown database-driven software applications with less than perfect construction. There is valuable application, data and domain information in the sql code and activity that occurs between the software and database, but it is often time-consuming and difficult to retrieve.

Our solution - Collect, breakdown, store and catalog query details for instant retrieval to unlock the schema, domain and software information within.

Customer - Anyone wanting to catalog query work for future reference to reduce duplication of effort. Anyone seeking “domain knowledge” or to understand the inner workings of unknown third-party or custom software applications driven by back-end databases that have less than perfect design.

This could include Business IT Application Support, Software Application Consultants, Business power users writing queries or exploring databases.

We do have a generic query parser, which automatically identifies relationships, and fields, and what not. At this point parser is not looking at foreign/primary key constraints at all. We even have a visual query builder for this sort of things. But it is us.

Now, if I’m a “power user”, in order to write a “query” I should have at least a basic knowledge about the schema (even less than perfect). I want to discover objects and fields, I want to see the data, I want to clean the data, de-normalize, normalize, etc. Actual “query” is a distant target.

Again, I don’t want to discourage you. The product looks good. If you can find a customer - great and I wish you all the best.

As stated by the previous comments… I too fail to see the benefits for me… I am a developer and deal with the typical developer queries…

I looked at it an thought dba tool? Newbie tool? Not sure but I did not click on any features that would make me, the developer want to buy it.

Instead of listing what it does, you should instead list what it solves…

Just my 2 cents.

Thanks again for the feedback and working through this with us. It is much appreciated. We are obviously sending the wrong message.

The tool isn’t directed at strict software developers that work on one or a few applications or database administrators. It is more for an analyst or application support role or possibly developer that works with multiple or even many applications with back end databases they did not build. They use the database to understand the application for support, fixing issues, or writing reports, possibly code.

There may be a team that doesn’t want to waste re-writing the same queries over and over and need to share them or to bring new or junior members up to speed. The individual may support enough applications that they can not remember the details of all of them, but want to be able to instantly retrieve work they’ve done in the past rather than re-writing the query every time. Or they may be doing a project to replace or re-write an application they’ve not worked with before and need to understand what is there. You can take hours asking users a thousand questions to try to understand and get part of the answer. This tool doesn’t necessarily replace that process, but it can very quickly add significant time-savings and value to it.

I think many software professionals working for businesses that have 3rd party and custom applications driven by a database understand the value of the technical makeup of these databases and how much it can help you implement, upgrade and support these systems. Our tool is intended to provide significant help with the process of discovering and retaining that technical information about the database.

How about this…

Get rid of “write queries, we can help”, I believe this is misleading, making people think we are trying to help with the actual typing of the query when we are really trying to help with the information you need to develop the query.

Add something like this…

Find and share sql queries

A tool for software analysts and application support professionals to find, organize and share sql query code.

Do you spend time writing sql that you know has been written before?
Do you spend time hunting for relationship, join, table or field details in unknown databases with less than perfect design?
Does your team write different versions of the same sql query over and over?
Do you spend time hunting through databases, sql scripts, code, spreadsheets or Access files for sql code?

If you answered yes to any of these questions, Sql Caddy can help you.