Best scenario for enterprise ArcSDE for SQL Server geodatabases

[AllesioRobbiani]

Hello,

A medium-sized municipality (250,000 inhabitants) considers setting up its basemap in a centralized ArcSDE 10 repository. Currently there is an Default instance of SQL Server 2008 R2 with a bunch of non-spatial databases. Ideas about setting up the enterprise geospatial repository gravitate toward creating two geodatabases, one to house the rasters (250 GB of aerial imagery), and another strictly for vertor/tabular geodata (parcels, ownership, streets, boundaries, etc.). The dilemma is to create a new SQL Server instance strictly for GIS, or to create the two geodatabases into the existing Default SQL Server instance? Evidently the GIS people lean toward their own, while the IT guys are weary about potential increases of the SQL Server licensing cost, and added operations expenses. What is your experience? Are there any best practices papers or other practical an reputable information sources that you used when setting up your enterprise ArcSDE geodatabase(s)?

Thank you,
Allesio

[JonDeRose]

The best answer is...it depends.  The questions I would ask myself are:

1) Is my IT staff dependable and responsive to the GIS staff's needs?
2) How much control do I need over my configuration outside of ArcSDE?

There are many objects to consider here but if licensing costs are a big hurdle to cross and your IT group plans on managing the server the bets bet would be to move forward using a 'SDE' schema geodatabase which would enable granular access to the GIS staff to access and manage the ArcSDE geodatabases while not stepping on the toes of the IT department.

It would be a good idea to separate this data into two databases as you have outlined.  The raster database will not be updated frequently and will also not be edited, therefore it may use a different recovery model (SIMPLE).  Separation will make backup and restore operations on your vector database much easier to manage.

The decision to configure your own separate SQL Server instance will be entirely dependent upon who you wish to manage the actual server as you will require sysadmin to perform certain database administration functions not related to ArcSDE and to manage user logins and other operations that do require admin permissions on the database instance every now and then. 

I understand this is not a comprehensive response but the real answer unfortunately is that it depends on many things (of which company culture is a large one) and no two sites are alike.

- Jon