It is some time now, but I still remember a funny event related to an impotent SQL server. I was working with SQL server replication setting up the slave_exec_mode property of the SQL server. The slave_exec_mode property can either be set to 'strict' or 'idempotent' and I used search engines to find documentation. I wrote my search query and clicked the top search engine spell check example without verifying and for some reason I was searching for an 'impotent SQL server' instead of 'idempotent SQL server'.

The funny/sad story is that the following weeks I got Viagra and other health related commercials. If my SQL server was impotent I would definitely buy some Viagra and stuff it full. Luckily the server is only idempotent if I choose it to be.

Definition for 'impotent', a man abnormally unable to achieve an erection or orgasm

put Viagra in a man -> something changes
put Viagra in a man -> something changes even more
put Viagra in a man -> something changes evvveeeenn more

Definition for 'idempotent', a property of operations such that no matter how many times you execute them, you achieve the same result

put Viagra in cpu fan -> fan is stuck
put Viagra in cpu fan -> fan is stuck
put Viagra in cpu fan -> fan is stuck

The conclusion of the story is that somebody/something decided that one search query for SQL + impotent was enough to activate commercials totally out of context. Please note that every search query before and after was non-health, technical and SQL server related.

Humans runs companies. Humans got responsibilities within these companies. Can we please create sane solutions for humans?

If or when I need Viagra I will provide some non-SQL health related search queries.

Happy searching