Scribd
Upload
7 views2 pages

SQL Server Upgrade Strategies Guide

The document compares two upgrade methods: in-place and parallel upgrades. In-place upgrades require minimal effort and downtime, with automated configuration changes and no data transfer, while parallel upgrades necessitate planned efforts, manual migration, and potential downtime. Additionally, parallel upgrades allow for more flexibility in server architecture and easier rollback processes.

Uploaded by

arjun g
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views2 pages

SQL Server Upgrade Strategies Guide

The document compares two upgrade methods: in-place and parallel upgrades. In-place upgrades require minimal effort and downtime, with automated configuration changes and no data transfer, while parallel upgrades necessitate planned efforts, manual migration, and potential downtime. Additionally, parallel upgrades allow for more flexibility in server architecture and easier rollback processes.

Uploaded by

arjun g
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Action Item In Place Upgrade Parallel or side by side upgrade

Upgrade Efforts  Minimum  Efforts needs to be


 Upgrade is Automated planned
 No data  Manual migration
migration needed  Data migration required
Downtime  Requires downtime  Minimum or no
downtime required
 Production will be online
while migration is taking
place
Configuration Changes  Configuration changes  All configurations needs
are Automated by the to be preserved and
system migrated over to new
 Application SQL Server instance
configuration is not  Applications needs to
needed since it change configuration to
would use same connect to new SQL
connection Server instance
information  Requires manual
check of all
configurations (system
and user)
Data Transfer  No Data  Data Transfer required
Transfer and can be planned in
required staging manner
 All Server integration  All server integrations
changes remains intact needs to be created over
and gets upgraded by to new SQL Server
the system (Replication, Instance
Mirroring, Linked
Server and SQL Server
Agent
Jobs etc.
Server Name and IP  No changes in Server  Server and IP
and SQL server address will change
instance  All application needs to
 Application can continue change their connection
using same server Name to connect to new server
and IP address with new IP address
Testing  Testing is relatively  Thorough testing
faster as same testing required as there are
script and be used chances to a
once upgrade is configuration mismatch
completed  Testing needs to be
planned and new
testing script required
since Server Instance
has changed for testing
script
Rollback  Rollback usually is  Rollback is very easy as
rebuilding the whole production system
system remains online during
 Requires backup of all migration, if testing fails,
configuration, databases it can be remediated
including system with no downtime
databases required and all
application can connect
to previous Online
production system
SQL Versioning and Architecture  Versioning upgrade  Since it would be new
would be possible with install, any version
same architecture (32 bit with any architecture
to 32 bit), 32bit to 64 bit can be installed and
is not supported tested

You might also like