This is an incredibly interesting topic and it appears there are pros and cons for scripting / not scripting. I almost always press the script button when I am doing something in SQL even just to check what it thinks it is going to do if I press the commit button. It may be overcautious but it is also how you gain confidence and understanding.

If the script button it is going to generate what it is going to run then how can the system generate buggy scripts? I have never seen this. It may generate scripts which are complicated and not palatable to understand or scripts which may error or take to long because of the data you have.

If you take the time to understand them then you have learnt something new and gained a better understanding of the environment you work in and eventually it all becomes an old hat.

The way I think about it is:

- If the task needs to be repeated more than twice then there is no question a script should be generated.

- Scripts can be reviewed by piers. No one in this day and age should live in a bubble.

- Scripts can be tweaked if necessary.

- A script may product some in-site into the system and make you think of a better way to complete a complex task.

Some of this borders on DevOps, if it is truly a regular / repeatable task then it must be scripted.