@Thaddy You are absolutely right....
... if the goal is one set of compatible dlls per database server and the idea not to pollute the project environment.
And that you are confident that the future target environment in which the programme will run is installed correctly and that there are no side effects to already installed libraries and applications.
I prefer not to pollute the operating system, especially that of the customer. That's why my programmes come with all the necessary dlls in their own directories.
Of course, installation programmes could solve some of the problems mentioned, but not all of them.
In companies with centralised rights and installation management, things may look different, but for me, this strategy causes fewer problems, but of course everyone should do as they wish