Add Database Client Install to Server Install Documentation

12-28-2018 04:24 PM
Status: Open
New Contributor II

Just ran through the Enterprise Builder process to set up an Enterprise Base Deployment of 10.6.1 on Windows Server 2012 R2.  It's nice that the Builder packages up the install and makes it very convenient, but the documentation (also possibly the Server Install Guide) should include a post configuration reminder that you should consider also installing an Enterprise Database Client to the host server.  I just ran through a support case to have a Support Tech tell me that I hadn't installed a SQL Server Client on the server because my symptom was that I couldn't register an enterprise geodatabase in the ArcGIS Server data store.  There is reference to this in the part of the Server Documentation that talks about registering databases, but it's not in the installation guide portion of the documentation.  In step 8 of the Server Installation Guide, it talks about making your data accessible to ArcGIS Server, but it doesn't explicitly say you've got to have an Enterprise Database Client on the server to make that happen.

So, how about including reminders in the installation guides for Builder and Server that once you're done configuring the server applications, the SysAdmin should consider adding the appropriate Enterprise Database Client to the host server as a final step, because publishing map services on a fresh install isn't going to go well if the host ArcGIS Server can't see the Enterprise Geodatabases (yes that was a rhetorical statement). enterprise builderarcgis server and arcgis enterprise‌arcgis enterprise installation


Hi Richard,

Thank you for sending along this feedback. I am sorry to hear that you had to learn about installing the client libraries through a technical support case, and the information was not clear from reading through our installation guide. This is helpful for us to know moving forwards. 

Thank you,




Thanks for commenting on my idea.  My support case analyst suggested that I put this item into Ideas after she and I chatted about my experience and I pointed out that it wasn't mentioned in the installation guides.  I'm a newer GIS Sys Admin, with 30+ years of ESRI desktop/workstation experience.  So for some GIS Sys Admins the notion of putting the appropriate SQL client on the server is second nature, but for newer GIS Sys Admins, we're carefully looking at the documentation and installation guides.  So my fresh eyes on this caught what I believe is missing information in the installation guides.  Hope the Idea was helpful.