Service Request Form
[Project Name]
1) General Information
Project Name Test Solarwinds Environment
Submitted Date 05/28/2020
Received Date
2) Stakeholder Information
Name
Sponsor Jeff Miller
Stakeholder
Stakeholder
3) Project Scope
New X Enhancement ⃣
Description of Request/Project
(Provide an overview of the
project)Deliverables (What should
be delivered at the end of the
project)
Primary Objectives
(Select all that apply)
Impact to Users in More Than One
Department? If Yes, How?(List all
anticipated departments Impacted)
List all knownInterfacing Systems
(i.e., Email, Website, Intranet,
other)
Include web links to additional
Supporting/ Reference Documents
Additional Information/Comments
Design Approach : Always on is the recommend design approach as it is one of the most new design feature and can be implemented
clusters are something awesome: they take something like the customer’s SQL server and separate it from the hardware it’s running
on.
But the negative of cluster is cost.
To implement this I recommend 2012R2
This is a simple scenario topology with two data centers, each hosting one replica of the AG on a two-node
Proprietary & Confidential
Requested By SageNet IT
Requestor Dept. IT
Requested Start ASAP Requested End
To be Completed by PMO
Review Date Project Manager
How will the Stakeholder Organization benefit from this
Business Unit
request?
IT Test Environment for SolarWinds
Maintenance ⃣ Break-Fix ⃣ (See Definitions Below)
New SolarWinds Environment for testing. Uses SQL Server for the back end. Current
Production SolarWinds Environment involves a 2-node SQL 2017 Standard in
AlwaysOn configuration. Phase 1 of this deployment will be the SQL Deployment.
X Align to Corporate Strategy ⃣ Save Costs via Efficiencies ⃣ Generate Revenue
⃣ I Improve Customer Service ⃣ Reduce Working Capital X Improve Quality
X Remain Competitive ⃣ Other Physical security
and safety
Please further explain your Primary Objective selections :
Yes,If SQL server built as standalone instance there will be an imPact to users incase of any
server down or datacenter down scEnarios and it requires a huge downtime to rebuild entire
server from scratch.
There are mulitple DR solutions offered by microsoft and one of them is Always-ON.
If we choose AlwaysOn as a DR solution then there will be very less down time and users will
be routed to secondary datacenter incase of primary server goes down.
Exhange, reportin services, integration services, analysis services. Web servers, share
point,Third party vendor applications, network, Firewall.
https://docs.microsoft.com/en-us/mem/configmgr/core/servers/deploy/configure/sql-server-
alwayson-for-a-highly-available-site-database
https://docs.microsoft.com/en-us/sql/database-engine/database-mirroring/database-mirroring-
sql-server?view=sql-server-ver15
https://docs.microsoft.com/en-us/windows-server/failover-clustering/create-failover-cluster
It will be better to choose either AlwaysON or Clustering to cover both HA and DR solutions.
Incace of any server crash or catstrophic events we can switch from primary to secondary
databcenter with less down time and data loss.
Page 1 of 2
Service Request Form
[Project Name]

Multiple data centers

• Multiple replicas, up to five including one primary replica and one to four secondaries
• More than two nodes in each, if additional passive nodes are desired for HA purposes
• Not all of the replicas in an availability group need to reside on FCI instances; some replicas can reside on non-FCI stand-
alone SQL Server instances
• Multiple availability groups based on the logical grouping of databases for your application environment

You can use this solution to replace topologies that use database mirroring and log shipping.

Successful deployment of such an HA/DR solution involves not just the DBA team, but close collaboration between the DBA team,
Windows Server administration team, and the networking team in the IT organization. skills is very valuable when you deploy the
HA/DR solution

Instructions:
Please complete this document and obtain the sponsoring Vice President’s Approval via email.
Forward the approved document and any related questions to: PMOSR@SageNet.com

Definitions:
New Any technology capability that is to be purchased or developed that does not exist within a department having stated requirements.
(Provides New Business Capability).
Enhancement Any change to existing technology within a department having stated requirements. (Increases Business Capability).
Maintenance Any technology that requires production support, patches, backup, and performance tuning. (No change in Business Capability).
Break-Fix Restore existing Business Capability. (No change in Business Capability).

___________________________________ _________ ___________________________________ ________

VP-LevelSignature Required Date Signature Date

____________________ _____________ _________ ____________ _____________ __________________

Printed Name Title Printed Name Title

Proprietary & Confidential Page 2 of 2