Why does the initial install of SEP 14 need SQL SA access?

I'm in the process of setting up my production SEPM 14 infrastructure, and when requesting a new back-end SQL DB, I received push back from our DBA's asking what "exactly" the installer was doing that required SA access.

Before I put in a support case to ask this question, I was hoping someone in the forum could offer some insight...or point me toward a document that would have this information.

From what our DBA told me, some vendors make configuration changes to the server that could affect other databases that share the same server. His goal is to understand what the SEPM 14 installer is doing to prevent this from happening.

Thanks for any thoughts,

-Mike