• ethouin 94797 - Thursday, September 13, 2018 10:15 AM

    Thanks Steve for the feedback! 
    As demonstrated in the Demo Video, AppDB.Studio is basically a SQL script generator that aims to standardize how developers build Databases, fixing forgotten FKs or naming conventions, helping refactor Models, etc. So users do have the means to fix any issues should they come up, it's all in the generated SQL scripts and nothing's hidden. 
    Yes, our tool could break or have bugs, but I don't think that's reason enough to stop building tools for people. We'd fix issues and move on. Microsoft's own tools are not exactly bug-free....  😉
    Consider this: 
    According to last week's RedGate's Blog article, "76% of developers are now responsible for both application and database development", by our experience that mostly means that Web Devs build databases nowadays. Unchecked, we think that's the real danger. Right now, there's no tool on the market that helps the "Occasional" Database Developer apply good practices, and that's what we're committed to provide for them.
    What do you think?
    If you still feel there's a danger to fear here, could you detail it a bit more?

    I don't have time for a product demo at the moment, but I would have to believe that the claim to "change database objects without breaking dependent applications" seems a tad strong and might just rely on creating synonyms, which has it's own set of risks.   However it's done, that product, on it's own, doesn't provide the expertise to understand the scripts it generates, or the consequences of implementing same, and potentially places such less skilled personnel in a much less good position of having implemented something they don't understand and might not have the skill to fix....

    Steve (aka sgmunson) 🙂 🙂 🙂
    Rent Servers for Income (picks and shovels strategy)