Post reply

The Problem Isn't Always Your Query or Schema... Sometimes It's Hidden Assumptions

  • April 6, 2026 at 12:00 am

    #4754563

    Comments posted to this topic are about the item The Problem Isn't Always Your Query or Schema... Sometimes It's Hidden Assumptions

  • April 7, 2026 at 12:10 am

    #4762228

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • April 7, 2026 at 5:01 pm

    #4762610

    There are some good points here.

    Getting realistic production data is the bane of my existence.  Generating data is easy.  Generating data that represents what happens in Production is not.

    We have a CICD database that contains a limited amount of happy path data, and data that has been discovered in the production environment that has caused functional errors.  Where possible, we depersonalise the data so it can be used for development, but make sure whatever caused the error in production has an equivalent.

    The CICD database is small and grows very slowly.  As it is depersonalised, we have a workflow that allows developers to tear down their personal development databases and rebuild them from the CICD database.  That way, we have eliminated an environmental difference.

    I like the idea of measuring data distribution differences between production and other environments.

     

    LinkedIn Profile

  • April 7, 2026 at 10:06 pm

    #4762703

    Many times a developer may model a new stored procedure by copying an existing one as a template. This may leave variables that are not used and calls to other procedures whose results are not used. So taking a high level view as to intent versus what is happening is a good idea.

    ----------------------------------------------------

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply