---
title: Test Study for a Network Information Management System Gas Utility (SQL Server)
description: Test study for a Network Information Management System gas utility in AWS on SQL Server
content_type: test-studies
source_url: "https://architecture.arcgis.com/en/architectures/network-management-gas-sqlserver/physical-architecture.html"
md_url: "https://architecture.arcgis.com/en/architectures/network-management-gas-sqlserver/physical-architecture.md"
---
# Physical architecture
This architecture was designed with:
- A small/medium-sized gas utility in mind
- Support for [workflows](/en/architectures/network-management-gas-sqlserver/tested-workflows.md) with a target design load as described in the [test methods](test-results.md) section
- An enterprise geodatabase configured with Microsoft SQL Server
- AWS cloud infrastructure

The system was designed for and [tested](/en/architectures/network-management-gas-sqlserver/test-results.md) against the specified workflows, with adjustments to the machine types and sizes as needed based on test results.

![Physical architecture for a Network Information Management System: Gas Utility (SQL Server)](https://architecture.arcgis.com/assets/images/test-studies/nims-wl-gas-sqlserver.png "Physical architecture for a Network Information Management System: Gas Utility (SQL Server)")

_Download a [Microsoft Visio file](/assets/diagrams/nims-wl-gas-sqlserver.vsdx) of this architecture._ 
_Learn more about [diagramming resources](/en/framework/architecture-practices/architectural-foundations/diagramming-resources.md) for ArcGIS systems._

> [!NOTE]
> **Note**
> For more information on the software components and key interactions in this architecture, please review the Network Information Management System [reference architecture](/en/architectures/network-management/logical-reference-architecture.md).
# Machine types and sizes

The following represent the machine sizes chosen and validated for the scope and purpose of this test study. However, it is highly recommended to follow a complete design process to account for your business and technical requirements.

Esri offers [system architecture design](https://www.esri.com/en-us/arcgis/services/consulting) services should you need help determining all of the different factors relating to your organization's physical design- such as networking, storage, system environments, and sizing. Minimum system requirements for each component are listed in the respective software [documentation available online](https://doc.arcgis.com/en/).

#### Desktop (ArcGIS Pro & web browser)

| Spec | Value |
|---|---|
| Machines | 3 |
| Instance type | g4DN.xlarge |
| CPU | 2 CPU (4 vCPU) |
| RAM | 16 GB |
| GPU | 16 GB |
| Storage | 128 GB |


#### Portal for ArcGIS 

| Spec | Value |
|---|---|
| Machines | 2 |
| Instance type | m5.xlarge |
| CPU | 2 CPU (4 vCPU) |
| RAM | 16 GB |
| Storage | 128 GB |


#### ArcGIS GIS Server 

| Spec | Value |
|---|---|
| Machines | 2 |
| Instance type | m5.2xlarge |
| CPU | 4 CPU (8 vCPU) |
| RAM | 32 GB |
| Storage | 128 GB |


#### ArcGIS Server (hosting server) 

| Spec | Value |
|---|---|
| Machines | 2 |
| Instance type | m5.2xlarge |
| CPU | 4 CPU (8 vCPU) |
| RAM | 32 GB |
| Storage | 128 GB |


#### ArcGIS Data Store (relational) 

| Spec | Value |
|---|---|
| Machines | 2 |
| Instance type | m5.xlarge |
| CPU | 2 CPU (4 vCPU) |
| RAM | 16 GB |
| Storage | 256 GB |


#### ArcGIS Web Adaptor

| Spec | Value |
|---|---|
| Machines | 2 |
| Instance type | m5.large |
| CPU | 1 CPU (2 vCPU) |
| RAM | 8 GB |
| Storage | 128 GB |


#### ArcGIS Monitor 

| Spec | Value |
|---|---|
| Machines | 1 |
| Instance type | m5.2xlarge |
| CPU | 4 CPU (8 vCPU) |
| RAM | 32 GB |
| Storage | 128 GB |


#### File storage 

| Spec | Value |
|---|---|
| Machines | 1 |
| Throughput | 64 MB/s |
| Storage | 1 TB |


#### Database 

| Spec | Value |
|---|---|
| Machines | 1 |
| Instance type | r5.2xlarge |
| CPU | 4 CPU (8 vCPU) |
| RAM | 64 GB |
| Storage | 256 GB |


#### Domain server

| Spec | Value |
|---|---|
| Machines | 1 |
| Instance type | m5.large |
| CPU | 1 CPU (2 vCPU) |
| RAM | 8 GB |
| Storage | 128 GB |


# Additional infrastructure considerations
The following are additional areas of consideration when designing a Network Information Management System and an explanation of some infrastructure choices made for this test study.

### Application load balancer (ALB)
At least one third-party load balancer is required in a highly available ArcGIS Enterprise deployment- they handle client traffic to your portal and server sites and internal traffic between the software components. Although the ArcGIS Web Adaptor is considered a load balancer, it is insufficient on its own to serve as a load balancer in a [high availability](/en/framework/architecture-pillars/reliability/high-availability.md) configuration. Therefore, in this test study, an Amazon Web Services (AWS) Application Load Balancer was used.

### Database consideration
For the scope and purposes of this test study, a choice was made to deploy SQL Server on a virtual machine (EC2). However, depending on your needs, you might consider leveraging a database platform service like [RDS (Amazon Relational Database Service)](https://enterprise.arcgis.com/en/server/latest/cloud/amazon/create-geodatabase-in-amazon-rds-for-sql-server.htm) or [SQL Managed Instance](https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview?view=azuresql) in a Microsoft Azure environment.

### Shared storage
To successfully implement a highly available ArcGIS Enterprise deployment, the configuration stores must be stored in a highly available, shared location. This ensures this data remains accessible even if one server fails, providing uninterrupted service to end-users. Additionally, shared storage simplifies data management in a multi-machine deployment and improves scalability by centralizing data storage and allowing for expansion as needed.

### System components not included in the diagram
Note that while antivirus software and AWS networking components are not illustrated in this diagram, they were present in the test study.