How to obscure confidential data/code while retaining functionality for forum posts
Hi, I am running into an issue where I'm getting "A severe error occurred on the current command." when trying to insert a row into a replicating table. Most of the insert statements run fine, but this one throws this error. I would like to post about it to ask for troubleshooting suggestions, but it's important that I obscure the substantive information in the statement to keep the data confidential. This is an issue I run into quite often. Does anyone know of a fast way to convert a SQL statement to obscure confidential data, while preserving the substantive parts of the statement (and ideally maintaining some readability for those reading the posts)? I can do it manually, of course, but that is quite tedious. I'd greatly appreciate any advice anyone can give.
I think it needs to be done manually. For the sake of presenting it accurately to the community, you want to keep it as close to the original as you possibly can while hiding the confidential data. Even if you had software that would say change every column name in a consistent way, you would not want to use it. You would instead want to change only what you knew needed to be changed and even then change it to something that would still convey thins like data type and relationships. And you would not want to automatically change string literals to random things, but rather to something related but fake, and that is hard to automate in any general way.