SAP Platform Modernization

with Microsoft
Microsoft Partner Enterprise Architect Team
(PEAT)

1
Agenda

Topic Time
Summary of the past SAP discussions between Kwik and
1 8:00 am 8:30 am
Microsoft
8:30 am 11:00
2 SAP on SQL Server Update
am
11:00 am 12:00
3 SAP on Windows Server / Infrastructure Update
pm
4 SAP Platform Migration 1:00 pm 3:30 pm

5 SAP and Microsoft Business Intelligence and SharePoint 3:30 pm 4:00 pm

6 Summary and Next Step 4:00 pm 4:30 pm

2
 Microsoft: An industry leader
Microsofts comprehensive hybrid story, which spans
applications and platforms as well as infrastructure, is
highly attractive to many companies, drawing them
towards the cloud in general.
Lydia Leong, Gartner

Microsoft leads everywhere

Social Software in Workplace (Oct X86 Server Virtualization (Aug Public Cloud IaaS (Aug 2016) Operational DBMS Systems (Oct BI and Analytics Platform (Feb
2016) 2016) 2015) 2016)
Microsoft
Microsoft
Microsoft Microsoft

Microsoft

3
 CHALLENGES WITH BUSINESS APPLICATIONS

User
Performance Experience ?
?

Availability IT Efficiency ? Total

? Costs ?
44
55GOALS
GOALSOF
OFMODERNIZATION
MODERNIZATION

In-memory Maximized
Real-time User
Performance Productivity

Total Costs
Fully Migration
Sky-high
Managed Risks
Availability
and Mitigated
Minimized
5 55
 TIER-1 APP MODERNIZATION ON THE CLOUD
Tier-1 Business
Users,
Rehost/Rewri
Applications Surround Information
te Workers

OS390/zO
S

Partner Cloud

EPG | MICROSOFT CONFIDENTIAL 6

Item Item 2 Current vNext Benefits
High level Diverse 30% total cost savings, Service level 30-50% total cost savings
optimization, Further governance
Busines Server pSeries, Intel Intel (IBM, HP, Dell, Cisco, Fujitsu etc) Cost saving (by 80%)
s apps
OS AIX, Windows Windows 2012 R2 Cost saving
-
SAP, Database Oracle SQL Server 2014 Enterprise 1) DB Compression (by 75%)
Java, 2) Cost saving (by 50%)
.NET, 3) HA/DR/In-Memory built-in
C, 4) RPO = zero, RTO = 3-min,
ISV
apps, & 1 hour (in case of DR)
BI etc Storage High-end + Mid-range Mid-range SAN and SSD Cost saving (by 50%)
SAN
WAN ? Shared, low bandwidth Cost saving
Tape Used ? None Cost saving
Consolidatio Virtualization ? % Virtualization over 80% Cost saving
n
Datacenter On-premise Hybrid (On-premise + Public Cloud) Cost saving
Vendor ? Proactive Enhanced service level
Support
BI tools Various Excel + SQL Server BI Enhanced productivity
Productivity/ No integrations between Integrations between SharePoint/Office Enhanced productivity
Portal SharePoint/Office and and SAP (ECM, BPM, Workflow)
SAP

7
 Customer Benefits of Microsoft Application Platform
Service In-memory, high availability and disaster recovery are all
Level built-in on MS platform - to achieve nearly 100 % DB cache
hit ratio,
over 99.995% OS/DB availability (including planned
downtime),
Zero
Cost RPO by
reduction and less
SAP than migration:
platform less thanTarget
3-min=RTO
by 40%
TCO - Commodity Intel servers (e.g. 40-core, 1TB RAM, 80K SAPS) and
mid-range SANs or flash memory storages can run all sizes of SAP
while compressing SAP databases by over 75%, reducing # of
operators,
data center space and power consumption through virtualization and
automation
Migration SAP platform migration is easy, smooth and risk-
free
- 3 or 4-month project
with a downtime of up to 2 days
8
In-MEMORY DATABASE COMPUTING PROVIDED BY SQL SERVER
(All BUILT-IN, No ADDITIONAL COST)
SQL Server is the only database (other than HANA) that SAP made it standard/default to
compress all ABAP tables and indexes
Database SAP on SQL customers can achieve DB compression by over 75%, which is 100% performance
positive
Compressio Database cache hit ratio is raised up to almost 100%, as x-large SAP tables are compressed,
n and current I/O bottleneck is eliminated
Up and running at : All SAP on SQL 2008 or later customers (e.g. Petronas, Singapore Ministry of
Finance, Lockheed Martin, NEC, Hitachi, Mitsui, Nikon, Bridgestone, Konica Minolta )

SQL Server is the only database (other than HANA) to which its column store is integrated with
SAP BW
Column Column Store Index boosts BWs query performance (e.g. by 4 5 times)
SQL Server 2014 column store indexes are modifiable/updatable
Store SQL Server R&D believe column store works well at DWH environment (e.g. BW) but *DO NOT* at
OLTP environment (e.g. Business Suite)
Up and running at China Light and Power, HomePro

Very large amount of physical memory (e.g. up to 4TB RAM) + flash memory storage
In-memory (including SSD) that replace traditional SAN Storage
In-memory reference models available from Dell, Cisco, HP and IBM
Hardware Up and running at : Quanta, NEC Fielding, Mitsubishi Heavy Industries

9
 High AVAILABILITY DATABASE COMPUTING PROVIDED BY
SQL SERVER (All BUILT-IN, No ADDITIONAL COST)

High availability and disaster recovery with SQL Server

2012/2014 AlwaysOn at a fraction of cost
Keep having synchronous or asynchronous replicas of SAP databases
Sync for HA within datacenter, Async for DR across datacenters
Customers can achieve zero RPO, 3-min or less RTO (issues within
datacenter) and 1-hour or less RTO (disaster, datacenter issue) without
affecting SAP application performance
Huge cost savings with wide area network and SAN storage, compared to
storage based replication, as not relying on enterprise SAN functionality
and only compressed transaction logs are transferred to DR site
(*) Partner Ecosystem
Microsoft investing in strategic alliance in backup, monitoring and
automation solution area (e.g. Tivoli, Openview, Veritas, NetIQ)
10
 10 METRICS Microsoft Platform CAN PROVIDE TO YOUR BUSINESS APPLICATIONS
(*) 40,000 SAPS, 512GBRAM : 35k USD/server
(*) 78 SAP customers in Asia modernized its
platform
(*) 70 SAP customers in Asia integrated with
1. 75% database compression with (*) 80,000 SAPS, 1TBRAM : 55k USD/server
(*) 80,000 SAPS, 1TBRAM, 6TBSSD : 110k
Column Store, 80% backup
MSBI
Business compression
USD/svr+stg
IT
2. 10-times larger server memory,
nearly 100% DB cache hit ratio
3. 100-times faster I/O with SSD

4. 1-sec user response time, Applic Applic 5. Zero RPO, 1-hour RTO for
***
10-times better batch ation ation DR
performance 6. Zero unplanned downtime,
8. 3-times better productivity Microsoft Platform
99.995% OS/DB availability
including planned downtime
9. 90% of end users use
Office, web and SharePoint 7. 30-50% total cost
10.Zero custom code within
reductions
to access applications apps
Computing
Computing Power
Power

On-premise
Partner Cloud
11
11
 Modernizing SAP Platform on Microsoft Cloud
All SAP Business Suite applications are fully multi-platform
OS
SAP system copy is export and import - no difference at all whatever OS/DB platform you migrate to
SAP has a standard tool kit for heterogeneous system copy (OS/DB change)
SAP on SAP on
HP- Windows/SQL Server
UX/Oracle

SAP on
SAP on Windows/SQL Sever

EXPORT
AIX/Oracle

IMPORT
on Azure VM

SAP on OS/DB SAP on

Linux/Oracle independent
Windows/Oracle
dump files
on Azure VM

SAP on SAP on
Linux/DB2 Linux/HANA
on Azure VM +
Azure Server for
HANA 12
 TOTAL COST REDUCTIONS THROUGH MIGRATION REAL EXAMPLE
Previous After
Cost
system's migratio
Cost to run SAP % %2 reduced Why cost can be reduced
cost/year n to MS
by (%)
(K USD) (K USD)

1) Utilization of commodity Intel x86 servers

2) Server consolidation w/ virtualization with Hyper-V
1) Server 300 22 80 10 73
3) SQL Server's built-in capabilities of high availability & disaster
recovery
1) Utilization of mid-range SAN storage instead of enterprise
2) Storage 300 22 160 20 47 model
2) SQL Server database/backup compression (by 75%)
3) Network 200 15 160 20 20 Switch to increasingly reasonable 10Gb Ethernet
4) DB Software Migration from UNIX/Oracle/DB2 with high maintenance costs to
150 11 100 12 33
maintenance Windows/SQL Server
Server consolidation, IT automation and standardization with
5) Internal
200 15 160 20 20 auto-tuned Windows/SQL Server (no memory tuning, no DB
Labour
defrag, no update stats..), Hyper-V and System Center
6) External
Labour and Data 200 15 150 19 25 Competitions among hosting vendors
Center
Total Costs 1,350 100 810 100 40
OS/DB migration of SAP and surrounding sub systems (e.g. UNIX
*) Migration - - 500 - shells) + Additional Software License -> investment return = 1
year
13
TOTAL COST REDUCTIONS THROUGH MIGRATION REAL EXAMPLE
Total Cost Reductions through SAP Platform Modernization
1,600

1,350
1,400

200
1,200

1,000
200
810
150 (40%
800
200
minus)
150

600 160

300 100
400
160

200
300 160

80
0
Previous system's cost/year After migration to MS
(KUSD/year) (KUSD/year)
1) Server 2) Storage
3) Network 4) DB Software maintenance
5) Internal Labour 6) External Labour and Data Center 14
Why SQL Server is THE BEST Choice for SAP APPLIACATIONS (1)
# Item What Microsoft Platform Can Provide
1 Server 1) MS platform has a variety of Intel x86 server
Cost platforms that are certified by SAP
2) SAP Solution Architect of Microsoft SAP
Solution Center can advise customer on server
sizing
2 Storage SQL Server is the only database that SAP made it
Cost default and standard to compress all SAP
tables Average compression ratio is over 75%
What customer get
IT can achieve better cost
performance than appliance
solutions by flexibly choosing the
very latest server platforms that
fits best to customers SAP
environment
1) IT can save costs on SAN storage
as SAP database size on SQL Server
is 25% or less of that on other
RDBMS

2) Mid-range SAN storage is

enough to run even X-Large SAP
instances
3 Performa SQL Servers database compression (for all End users feel better performance -
nce SAP applications) and column store index (for Entire SAP/SQL database is more
SAP BW) strongly help SAP application likely to be on memory and
environment achieve in-memory computing I/O bottleneck is more unlikely to
occur
4 Availabili SQL Server AlwaysOn functionalities allows SAP IT can achieve zero RPO,
ty application environment to have less than 3-min RTO and
one synchronous database replica for high over 99.995% OS/DB availability
availability & up to two async database replicas including planned downtime 15
 Why SQL Server is THE BEST Choice for SAP APPLIACATIONS (2)

# Item What Microsoft Platform Can Provide What customer get

5 Security 1) SAP Solution Architect of Microsoft SAP Solution
Center can provide customer worldwide best
practices on security for SAP environment
2) SAP has a single-sign-on capability with
Active Directory if SAP platform is Windows
Server
6 DB SQL Server licensing is very simple
Licensing (1) 8% of SAP application value (Runtime) or
Cost (2) based on # of cores for production
(Commercial) Never counts volume of server
memory
7 Vendor SAP Solution Architect of Microsoft SAP Solution
Support Center can provide customer worldwide best
practices on server sizing, storage design, HA/DR
design, OS/DB/SAP installations/configurations
and maintenance for the SAP environment
8 BI/DWH SQL Server has BI components (ETL, OLAP and
User Report) and partner solutions which allows to keep analysis of SAP data on Excel,
Experienc offloading data from SAP ERP to SQL Server so
e that end users can do analytics on Excel,
PowerPoint and SharePoint
1) IT can maximize security level
while keeping running SAP 24x7
and minimizing administrator
workload
2) End users feel better
experience in user authentication
In-memory database
computing is easier to achieve
on SQL Server
IT can proactively optimize the
service level of SAP application
environment while avoiding
unnecessary maintenance work
and system troubles
End users feel much easier to do
PowerPoint and SharePoint
16
Agenda

Topic Time
Summary of the past SAP discussions between Kwik and
1 8:00 am 8:30 am
Microsoft
8:30 am 11:00
2 SAP on SQL Server Update
am
11:00 am 12:00
3 SAP on Windows Server / Infrastructure Update
pm
4 SAP Platform Migration 1:00 pm 3:30 pm

5 SAP and Microsoft Business Intelligence and SharePoint 3:30 pm 4:00 pm

6 Summary and Next Step 4:00 pm 4:30 pm

17
 SQL Server 2016: Everything built-in
Industry leader in Most secure Highest End-to-end In-database
Mission Critical database performing data mobile BI on any Advanced
OLTP built- built- warehouse built- device built- Analytics built-
in in in in in
Industry leader 6 years in a row #1 performance A fraction of the cost R + in-memory
least vulnerable $2,230
80
69
70
SQL
60 Server
49 SQL
50 Server
43 SQL
Server
40 34

30
29 $480
2220 22
18
20 15 $120
Oracl
6
e
#1
10 4 5
3 1 3
0
#2 #3 is #5 Microsoft Tablea Oracle
0 0 0
2010 2011 2012 2013 2014 2015 u
SQL Oracl MySQL SAP TPC-H Self-service BI per at massive scale
Server e HANA
user

In-memory across all workloads

Consistent experience from on-premises to

cloud
The above graphics were published by Gartner, Inc. as part of a larger research document and should be evaluated in the context of the entire document. The Gartner document is available upon request from Microsoft. Gartner does not endorse any
vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner's research
organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.
National Institute of Standards and Technology Comprehensive Vulnerability Database update 10/2015
TPC-H 10TB non-clustered results as of 04/06/15, 5/04/15, 4/15/14 and 11/25/13, respectively. http://www.tpc.org/tpch/results/tpch_perf_results.asp?resulttype=noncluster
18
The road ahead with SQL Server 2016
Key enhancements for your SAP workloads
Memory-optimized columnstore =
real-time operational analytics for BW and ECC
Stretch database footprint size + saves on hardware &
storage
HA enhancements including failover multiple databases,
load balancing of asynchronous replicas and faster failover
Support SAP Core Data Services = efficiencies through logic
pushdown to the DB
Query Data Store for reliable performance
Interoperability = native & supported connectivity at the
app layer (Power BI, SSIS) SQL Server 2016

19
(*) SAP Support Pack Stack for SQL Server 2016

SUPPORT PACKAGE STACK

SAP SOFTWARE
(SPS) requirements
SAP NETWEAVER 7.0 SPS 33 (SAP_BASIS SP 33)
SAP EHP1 FOR SAP NETWEAVER 7.0 SPS 18
SAP EHP2 FOR SAP NETWEAVER 7.0 SPS 18
SAP EHP3 FOR SAP NETWEAVER 7.0 SPS 17
SAP NETWEAVER 7.1 SPS 20
SAP EHP1 FOR SAP NETWEAVER 7.1 SPS 15
SAP NETWEAVER 7.3 SPS 14
SAP EHP1 FOR SAP NETWEAVER 7.3 SPS 17
SAP NETWEAVER 7.4 SPS 12
SAP NETWEAVER 7.5 SPS 01

20
Microsoft IT - SAP ERP By The
Numbers
Deliver Reliant &
Agile ERP Platform
Enable Modern
Experiences
Provide Real Time
Processes

Highly Uncompressed 300 Monitored 170

8TB compressed
size 34TB 4M Dialog
Batch
Transaction
database
Steps/Day
K Jobs/Month M steps/Month

Internal
SAP Surround 110 Users Named User Major First &
Strategy (Mostly 6K Accounts 96% Non-SAPGUI
Best Program
K Indirect Access
to SAP)
users

Seconds
Business Process 99.99 Raw
0.4 user
Expertise
SQL/Win
response
time 8% Uptime

5-7%
System Transaction Servers 250 Compressio Incident
2x growth in 2x volume ever 638 (mostly n Storage yearl Ticket
past 2 years 18 months virtual) TB Savings
y Reduction

High Quality Enterprise Service Offerings via SAP

21
Current SAP ERP Production
System
Windows Server Redundant Full usage of SAPs redundancy
High Failover Cluster
for SAP Central
networking
infrastructur
features: scale-out with logon
groups, batch server groups,

Availability Services
Instance
e RFC groups, etc.

Elimination of single points of PRICE

CI PRICE PRICE
12 SAP Application
failure VM
PRICE

Servers
VM
High degree of redundancy VM
Windows Server 2012
VM RFC
R2
guards against planned and DIA WEB

VM BTC VM 32 vCPUs
unplanned downtime SAP Central Instance VM 352
RFC GB RAM

Windows Server 2012 VM DIA WEB

VM BTC
R2 VM
VM 8 vCPUs, 88 GB VM
RAM
VM

Dual Databases VM VM
VM
Allows staggered upgrades
Instant release rollback XTremeI
O
XTremeI
O

Local hot standby

Automated failover Primary & Secondary Database
SQL Server 2014 SQL Server 2014 Spare servers for
Windows Server 2012 R2 high availability rolling
System is highly virtualized HP DL560 G8 feature: maintenance and
(87.5%) 4 x 2.1 GHz 12-core hyperthreaded
SQL Server peak load
768 GB RAM
AlwaysOn capacity handling
 Moving To Virtualization And Azure
Server Utilization Index
Disk Score
1 2 3 4 5 6
1 Frozen Cold Warm Warm Hot Fire
2 Cold Cold Warm Warm Hot Fire
3 Warm Warm Warm Warm Hot Fire
CP
U 4 Warm Warm Warm Warm Hot Fire
Sc 5 Warm Warm Warm Hot Fire Fire
ore
6 Hot Hot Hot Hot Fire Fire

CPU Score Total % Proc Disk Score Avg. Disk Transfer/sec

1 <=2% 1 <=10
2 >2% and <=5% 2 >10 and <50
3 >5% and <=20% 3 >=5 and <200
4 >20% and <=70% 4 >=200 and <1,000
5 >70% and <90% 5 >=1,000 and <10,000
6 >=90% 6 >=10,000
23
Our Cloud Adoption Approach
Roadmap planning
~30% From To
Retire it, right-size, eliminate environments Office 365
Office servers
Portals and SPS SharePoint Online
Use or convert to a SaaS Any relationship CRM Online
(1st or 3rd party) solution ~15% mgmt VSO
Active Source ADL + PowerBI
Control & WIT Best 3rd-party
Expose functionality in SaaS
Data warehouses
existing SaaS/PaaS solution Industry standard
verticals
Convert to Azure PaaS solution

Optimize for and move ~35% ~10% ~5%

to Azure IaaS VM
First to move Next to move Hard or costly
No change, lift n
Basic web apps High I/O OLTP to Move
shift to IaaS
Advanced portals Regulatory and HVA Systems
Any new solutions high business PKI Systems
Any re-architected impact
Remain Legacy source
solutions control
on- <5%
premise Azure IT Roadmap
24
The Road To Virtualization And Azure
In 2014: Mid 2016:
520 Servers 1% Physical Hardware
61% Physical Hardware 64% On-Prem VMs
39% On-Prem VMs 35% Azure
9% 1%
11%

35%
39%

61%
64%

80%

Physical Servers On-Prem VMs Azure

 Physical
Virtualize
Microsoft SAP System Landscape June 2016 d
Azure VM

ERP GTS BI BOBJ SCM CI/ MDG CFM OER ADS OER DUET SOL
DS RMCA E-REC 1DSC CC OEM XI/PI GRC
Prod.

UA
Quarterly T
Release
SIT
Systems

DE
V

Prod. QA
Quarterly Release
Support, OOC,
& Monthly DE & Prod. Support
V

Sandbox
CASE STUDY : MICROSOFT IT - BENEFITS
Global SAP single instance with 8TB DB
and 100K internal/external users
to run Microsofts line of business - supply chain,
finance and human resources

Maximized service level

Zero RPO, Less than 3-min RTO,
99.998 % OS/DB availability including planned
downtime

Minimized TCO - utilizing

Intel commodity servers, DB compression, mid-
range SANs without a dedicated DBA
27
27
 Compressio
n

SQL Server Database Compression for SAP

SQL Server is the first RDBMS that SAP made it default to
(page-)compress all the SAP ABAP tables
Now page compression is SAPs standard
recommendation to all size of SAP/SQL Server
instances, even if over 10TB
Many SAP on SQL Server customers experienced over 75%
database compression
6 TB uncompressed Oracle -> 1.2 1.6 TB on SQL Server

Page compression greatly help remove the current IO

bottleneck as I/O subsystem transfers data with compressed,
and help raise buffer cache hit ratio as the data is
compressed and stay on memory
So database compression is 100% performance positive
28
 Compressio
n
SQL Server Database Compression Results

Database
Original Compression size Compresse SAP
Customer Database Size Method after Comp d by System
Microsoft 1.5TB PAGE all tables 300GB 80% BW
CLP 2.3TB Page all tables 600GB 74% BW
Australian Customer in
Sales and Retail 505GB ROW all tables 140GB 72% BW
Kyocera Mita 1.6TB PAGE all tables 480GB 70% ERP
Wholesale customer in
Japan 8TB (Oracle) PAGE all tables 3TB 62.5% ERP
CHINT 2.5TB PAGE all tables 500GB 80% ERP
Ranbaxy 5.3TB PAGE all tables 900GB 83% ERP
8.6TB
Compal (Oracle) PAGE all tables 1.8TB 77% ERP
Coldwater Creek 5TB PAGE all tables 1TB 75% ERP
AGL 5.9TB PAGE all tables 1.3TB 78% ERP

Additional CPU consumption is ignorable on modern x86 servers

Data is more likely to stay in-memory as it is compressed by over 70%
Compression helps eliminate the current I/O bottleneck 29
 Compressio
n

Page Compression Case Study : Ranbaxy

Graph 1 : Shows I/O workload (KB READ/sec and KB
WRITE/sec) to the SAN reduces dramatically after page
compression as more data is held in SQL Server cache
(memory)

30
 Compressio
n

Page Compression Case Study : Ranbaxy

Graph 2 : Shows Buffer Cache hit ratio

before, during and after compression

Before During Online After Compression

Compression Compression

31
 Compressio
n

Page Compression Case Study : Ranbaxy

Graph 3 : Show DB Volume 5.533TB reduces to 0.964TB

a reduction of 82.6%. Storage, Backup, System Refresh and
Check DB savings

32
 Compressio
n

Page Compression Case Study : Ranbaxy

Intel Xeon Processor
processing power keep doubling
every 2 years and over-performing RISC/UNIX

Memory on Intel servers more and more reasonable

256GB RAM only 20k USD
and 1TB RAM 55k USD

SAP data/tables/indexes are compressed by over 75% on

SQL Server and they are more likely to stay on server
memory
achieving in-memory database computing
33
SAP HA/DR

High Availability
SQL Server AlwaysOn
SAP Central Services Clustering
Data Protection
SQL Server Backup
Network based Backup
SAN Storage based Backup
Disaster Recovery
SQL Server AlwaysOn
Azure Site Recovery
Security
Encryption
Hardening
Data Masking ?
TDMS
System Copy
SAP System Copy tool
DB backup/restore or detach/attach
SQL Server AlwaysOn, Log Ship 34
In-MEMORY DATABASE COMPUTING PROVIDED BY SQL SERVER
(All BUILT-IN, No ADDITIONAL COST)
SQL Server is the only database (other than HANA) that SAP made it standard/default to
compress all ABAP tables and indexes
Database SAP on SQL customers can achieve DB compression by over 75%, which is 100% performance
positive
Compressio Database cache hit ratio is raised up to almost 100%, as x-large SAP tables are compressed,
n and current I/O bottleneck is eliminated
Up and running at : All SAP on SQL 2008 or later customers (e.g. Petronas, Singapore Ministry of
Finance, Lockheed Martin, NEC, Hitachi, Mitsui, Nikon, Bridgestone, Konica Minolta )

SQL Server is the only database (other than HANA) to which its column store is integrated with
SAP BW
Column Column Store Index boosts BWs query performance (e.g. by 4 5 times)
SQL Server 2014 column store indexes are modifiable/updatable
Store SQL Server R&D believe column store works well at DWH environment (e.g. BW) but *DO NOT* at
OLTP environment (e.g. Business Suite)
Up and running at China Light and Power, HomePro

Very large amount of physical memory (e.g. up to 4TB RAM) + flash memory storage
In-memory (including SSD) that replace traditional SAN Storage
In-memory reference models available from Dell, Cisco, HP and IBM
Hardware Up and running at : Quanta, NEC Fielding, Mitsubishi Heavy Industries

35
 AlwaysON

SQL Server AlwaysOn

SQL Server AlwaysOn provides ultra high

availability and disaster recovery at a fraction
of costs
Can have up to 8 replicas of SAP database
SQL 2008 R2 : only 1 secondary
SQL 2012 : up to 4 replicas
Can have up to 2 synchronous replicas, one of which is
automatic failover partner
Witness unnecessary any more, Automatic failover possible
without witness
10 - 20 seconds for failover
Backup/CheckDB/Reporting possible on the replicas 36
 AlwaysON

Without SQL Server AlwaysOn

SAP cannot provide services if

DB server is down
SAP can lose transaction data
in case of SAN storage issues
Long downtime when doing
system update on DB server
No way to run SAP and DB
when datacenter is facing a
disaster
Server/storage based high
availability and disaster
SAP Application recovery are expensive
Servers
37
 AlwaysON

SQL Server AlwaysOn with SAP

Sy Sy
nc nc

1) Sync
Replica 2) Sync
+ Auto Replica
failover

As As
yn yn
SAP Application 3) Async c c
4) Async
Servers Replica
Replica
in DR site
in DR site
SQL AlwaysOn help keep having up to 4/8 replicas
38
of SAP database (1 sync+auto failover, up to 2 sync)
 AlwaysON

SQL Server AlwaysOn with SAP

(Simply)
Reconnect
1) Sync
Replica

X
Automatic
failover

SAP Application
2) Async 3) Async
Servers
Replica Replica
in DR site in DR site
In case of DB issues automatic failover should minimize
39
the downtime without losing transaction data
 AlwaysON

SQL Server AlwaysOn with SAP

X
Manual
failover

X
(Simply)
Reconnect

SAP Application
2) Async 3) Async
Servers
Replica Replica
in DR site in DR site
In case of DB issues automatic failover should minimize
40
the downtime without losing transaction data
 AlwaysON

AlwaysOn - Active Secondary: Enabling Backup On Secondary

R/W workload
Backups can be done
on any replica of a
Backups database
Backups on primary
Secondary replica still works
Log backups done on
all replicas form a
single log chain
Backups
Database Recovery
Advisor makes
Primary Backups restores simple

Secondary

41
 AlwaysON
Production TEST & DISASTER RECOVERY
DD DD
CC CC
Error msg
16-core 16-core Reconnect
256GBRA 256GBRA 1. Issue on App-ECC
M M 2. Error message shows up on SAP
APP- APP- GUI
ECC ECC
3. End user to simply reconnect
APP-EP APP-EP
APP-Sol APP-Sol

16-core 16-core 16-core

256GBRA 256GBRA 256GBRA
M
SCS-ECC
M
SCS-ECC M
SCS-EP
SCS-Sol
SCS-EP
SCS-Sol (1) In case of
DB-ECC DB-ECC
DB-ECC (2) (3) app server
DB-EP DB-EP (2) Sync DB-EP (3)
DB-Sol Pro DB-Sol (2) replic
a
DB-Sol (3(
Async
replic issues
d a
(Prod) (Prod)

Usr/
sap

42
 AlwaysON
Production TEST & DISASTER RECOVERY
Error msg DD DD
CC CC
Reconnect
16-core 16-core
256GBRA 256GBRA 1. Issue on SCS-ECC
M M
APP- APP-
2. Error message shows up on SAP
ECC ECC GUI
APP-EP APP-EP 3. Failover
APP-Sol APP-Sol
4. End user to simply reconnect
16-core 16-core 16-core
256GBRA 256GBRA 256GBRA
M
SCS-ECC
Fail M
SCS-ECC M
over
SCS-EP
SCS-Sol
SCS-EP
SCS-Sol (2) In case of
DB-ECC DB-ECC
DB-ECC (2) (3) SCS server
DB-EP DB-EP (2) Sync DB-EP (3)
DB-Sol Pro DB-Sol (2) replic
a
DB-Sol (3(
Async
replic issues
d a
(Prod) (Prod)

Usr/
sap

43
 AlwaysON
Production TEST & DISASTER RECOVERY
Error msg DD DD
CC CC
Reconnect
16-core 16-core
256GBRA 256GBRA 1. Issue on SCS-ECC
M M
APP- APP-
2. Error message shows up on SAP
ECC ECC GUI
APP-EP APP-EP 3. Failover
APP-Sol APP-Sol
4. End user to simply reconnect
16-core 16-core 16-core
256GBRA 256GBRA 256GBRA
M
SCS-ECC
M
SCS-ECC M
SCS-EP
SCS-Sol
SCS-EP
SCS-Sol (3) In case of
Fail DB-ECC DB-ECC
DB-ECC over DB-ECC
(2) (3) DB server
DB-EP DB-EP (2) Sync DB-EP (3)
DB-Sol Pro DB-Sol (2) replic
a
DB-Sol (3(
Async
replic issues
d a
(Prod) (Prod)

Usr/
sap

44
 AlwaysON
Production TEST & DISASTER RECOVERY
Error msg DD DD
CC
16-core
Reconnect
16-core
CC
1. Issue on Production Storage
256GBRA 256GBRA 2. Error message shows up on SAP
M M
APP- APP-
GUI
ECC ECC 3. Failover
APP-EP APP-EP 4. Async copy to DR restart
APP-Sol APP-Sol
5. End user to simply reconnect
16-core 16-core 16-core
256GBRA 256GBRA 256GBRA
M
SCS-ECC
M
SCS-ECC M
SCS-EP
SCS-Sol
SCS-EP
SCS-Sol (4) In case of
DB-ECC DB-ECC
DB-ECC Fail
over
DB-ECC
(2) (3) storage issues
DB-EP DB-EP
DB-EP (2) Sync DB-EP (3) Async
DB-Sol Pro DB-Sol(2) replic
DB-Sol New DB-Sol (3( replic
Prod
a
d a
(Prod) (Prod)

Usr/
sap

45
 AlwaysON
Production TEST & DISASTER RECOVERY
DD DD
CC CC
16-core 16-core 16-core
16-core
256GBRA 256GBRA 256GBRA
256GBRA
M M
M
APP-
shu
M
APP-
shu
(5) Planned APP- APP-
ECC ECC
ECC
tdo
wn
ECC
tdo
wn failover
APP-EP
to DR site (1)
APP-EP APP-EP
APP-EP
APP-Sol APP-Sol
APP-Sol APP-Sol

16-core 16-core 16-core 16-core 16-core

256GBRA 256GBRA 256GBRA 256GBRA 256GBRA
M M
SCS-ECC M M
SCS-ECC
M
SCS-ECC
SCS-ECC
SCS-EP SCS-EP SCS-EP SCS-EP
Shu Shu Shu
SCS-Sol SCS-Sol SCS-Sol
t
SCS-Sol
t t
dow DB-ECC
dow DB-ECC dow DB-ECC
Shu
DB-ECC DB-ECC DB-ECC
n t
n n
(2) (3) (2)
dow
n
DB-EP DB-EP (2) Sync DB-EP(3)
DB-EP DB-EP DB-EP (2) Sync
Async DB-Sol DB-Sol (2) replic
DB-Sol Pro DB-Sol (2) replic DB-Sol
DB-Sol (3( replic
a Test a
d (Prod)
a
(Test)
(Prod)

Usr/
sap

46
 AlwaysON
Production TEST & DISASTER RECOVERY
DD
CC
16-core 16-core
256GBRA 256GBRA
M M
(5) Planned APP- APP-
ECC ECC
failover
APP-EP
to DR site (2)
APP-EP
APP-Sol APP-Sol

16-core 16-core
256GBRA 256GBRA
M M
SCS-ECC
SCS-EP
SCS-Sol
DB-ECC
DB-ECC
(3)
DB-EP(3)
DB-EP
DB-Sol(3(
DB-Sol

47
 Column
Store

Column Store
Fetches only needed
columns from disk
SELECT region, sum (sales)
Less IO C
2
C3

Better buffer hit rates C1 C4 C5 C6

Processes column data in

batches
Highly efficient algorithms
Assuming that enough
memory is available to keep
column-store index in-
memory
48
SQL Server 2014 Writable Column Store Index

49
 Column
Store

HomePRO

50
 Column
In-Memory Optimized Column Store SQL 2014 for SAP BW Store

Index
Compression Size [GB] Size [KB] Data [KB] Index [KB] Data Comp. Comp. Percent Factor

Space savings NONE SQL_2005 34,8

36.481.29
6 14.534.760 21.946.536 NONE
21.523.44
10 *
NONE
10 *
201 0,5

ROW SQL_2008 20,5 8 5.696.472 15.826.976 ROW ROW 119 0,8

Reduced number of indexes PAGE 17,3
18.154.64
8 4.214.480 13.940.168 PAGE
10 *
PAGE 100 1,0
COLUMN
Better compression Non-Clu CS SQL_2012
Clu CS SQL_2014
6,3 6.609.696 4.164.768
2,4 2.466.624 2.466.624
2.444.928 PAGE
0 Column Store
-STORE

36
14
2,7
7,4
Column
64% space saving in example Clu CS + Archive 2,0 2.068.592 2.068.592 0 Store_ARCHIVE 11 8,8

(E-fact table with 100,000,000 rows)

~70% and more in real scenarios
(due to reorg effect)
Faster data load index re-creation on f-fact
(during DTP)
Less index maintenance on e-fact
(during cube compression)
Typically no aggregate rollup needed
Aggregates are still supported if needed

51
Prerequisites for Column-store

52
Convert F/E-fact tables to Writable Column Store

53
54
55
Recommendations for SAP BW on SQL Server
Scope : E-fact, F-fact table, Flat cube
E-fact (reporting), F-fact (data load)
Real-time cubes out of scope

Recommendation : Convert E-fact/F-fact cubes (except

for real-time cubes) from row-store to writable column-
store
Upgrade to SQL Server 2014 recommended
NetWeaver/BW 7.4 -> NetWeaver SPS : 10, BW SPS : 10 are required
Use SAP report MSSCSTORE
Can keep aggregates if needed

Run BW Index Repair after each data load

SQL Server rowgroup compression, index reorg are done in the background

Run BW Cube Compression as often as possible

BW cube compression faster with Column-store
Update statistics are done in the background 56
SAP HANA and what SQL Server on x86 servers can deliver

1. In-Memory (or Huge Memory)

Huge server RAM such as 512GB 2TB is now cheap with x86 Windows based
commodity servers
Memory Array Storage (e.g. Fusion IO, Violin Memory) is now scalable (up to
50TB) , reliable (high availability) and reasonable
2. Database Compression
We can commit all SAP customers database compression by 70-80% by using
SQL Servers page compression (SQL Server 2008 or later)
3. Column Store
SAP has started to support SQL2012/2014 Column Store Index for BW 7.x

(*) Other Functionalities

Scale-out, Integrations with SAP BW and ERP (e.g. In-Memory DSO,
In-Memory InfoCube, CO-PA Accelerator)
(*) Critical to emphasize the service level of HA/DR provided by SQL Server 2012
AlwaysOn 57
Agenda

Topic Time
Summary of the past SAP discussions between Kwik and
1 8:00 am 8:30 am
Microsoft
8:30 am 11:00
2 SAP on SQL Server Update
am
11:00 am 12:00
3 SAP on Windows Server / Infrastructure Update
pm
4 SAP Platform Migration 1:00 pm 3:30 pm

5 SAP and Microsoft Business Intelligence and SharePoint 3:30 pm 4:00 pm

6 Summary and Next Step 4:00 pm 4:30 pm

58
 Windows

SAP on Windows & SAP Note Update

Windows Update
Windows 2012 R2 now Generally Available
Windows Server 2012 R2 is Generally Available for NetWeaver App
lications April 2014

Windows Server 2012 R2 Features

Shared VHDX for SAP Cluster Disks
Hyper-V Replica now 30sec, 5min and 15min
Live Migration traffic compression and RDMA support
vRSS inside a VM
Gen2 VMs are more secure, EFI boot and PXE boot
Cross Hyper-V cluster migration
Preserve Quorum on Failback and Low Priority Cluster Node 59
 Windows

General Windows Server Availability for SAP

General overview exceptions possible

60
 Hardware

Update on hardware developments

We see more customers putting their SAP databases on
SSDs within SAN (shared storage)
Results usually in around:
1 milliseconds writing (hardly any change to rotating spindle)
2 milliseconds reading (drastic change to rotating spindle)
We do have several customers who moved their SAP
systems to FusionIO card or other in server SSD cards
Results in read/write I/O latency usually drop to 150-300
microseconds
New generation commodity hardware support huge RAM
sizes:
Most of our high-end customers are running on 512GB to 2TB
memory for SQL Server DB servers. 3-4TB configs will become
common 61
 Hardware

Update on hardware developments

Intel has released new IvyBridge generation
processors
Intel Xeon E5 v2: 2-socket
Intel Xeon E7 v2: 4 and 8-socket

2-socket Xeon E5 v2 ~56,000 SAPS

4 and 8-socket Xeon E7 v2
4-socket Xeon E7 v2 delivers ~135,000 SAPS
8-socket Xeon E7 v2 delivers ~260,000 SAPS
CPU Power and SAPS now no longer a gating factor on
performance
Intel servers out perform Power7+ significantly. UNIX
systems in decline 62
 Hardware

Intels LATEST X86 CHIP -

IVYBRIDGE

2-socket, 24-core, 51,650 SAPS 4-socket, 60-core, 133,570 SAPS

63
Dell PowerEdge Rack Server Site
http://www.dell.com/us/business/p/poweredge-rack-servers

On-premise server
specification:
2 socket (16 core per
socket = 32 cores)
Intel E5v3 rack
server with
24 x 32GB DIMMs =
768GB RAM,
2 x dual-port 10G
NICs &
2 x dual-port 8Gb 64
 Hardware

Flash Memory Storage

Violin Memory
http://www.violin-memory.com/
HW Partner : HP, Cisco, Fujitsu, Dell, IBM, Supermicro
Fusion IO
http://www.fusionio.com/
HW Partner : HP, Dell, Cisco, IBM, Supermicro
HP 3PAR
http://www8.hp.com/us/en/products/data-storage/d
ata-storage-products.html?compURI=1225854

Now owned by HP
XIO
http://xiostorage.com/products/hyper-ise/

Flash Memory Storage technologies now reliable enough to run the entire database 65
 Hardware

SQL SERVER ON FLASH MEMORY STORAGE

Compan SQL
y Flash Performance 2012
Purpose Server Cost benefit
name/lo storage enhancement Always
go On ?

Cost cut by 75%

DWH HP DL980 Violin 8X faster batch job No
Kodansh (compared to other
performance
a appliances)

Cost cut by 83%

Online Job
HP DL980 Violin 10 X faster online Yes
Search Site (compared to previous
En Japan performance
hardware)

Online travel
HP DL980 Violin 10 X faster online - Yes
booking site performance

B2B property
information HP DL980 Violin 48 X faster batch job - No
provider site performance

Online travel Fusion

9X faster query response
40.5 X better No
booking site IO performance density

Online gaming Fusion 10 X faster check 10 X better performance Yes

site IO database density

Immediate 100% ROI (one 66

9X faster query response, year),
 Hardware

Dell PowerEdge R910 + Fusion IO

ioDrive2 Duo
4-socket, 40-core Fusion IO ioDrive2 Duo
Intel Xeon E5 Processors 1.2TB (MLC)x 5
Attache
d in
PCIe
Gen3
slots

Server RAM : up to 2TB RAM

67
 Hardware

Fusion IO
Data access time (micro sec)

15k rpm SAS HDD 5000

SSD 3000

Flash Memory Storage

Fusion IO
with PCIe Connection 100 Attached in
PCIe Gen3 slots

74x Faster !! 68
 Hardware
Dell PowerEdge R820 + Fusion IO ioDrive2 Duo

Performance
Read Bandwidth (1 MB) : 3.0 GB/s x up to 5 (= up to 120Gbps)
Write Bandwidth (1 MB) : 2.5 GB/s x up to 5 (= up to 100Gbps)
Ran. Read IOPS - 4K : 480,000 IOPS x up to 5
Ran. Write IOPS - 4K : 490,000 IOPS x up to 5
Read Access Latency : 68s
Write Access Latency : 15s
Extensibility/Scalability
Up to 5 Fusion IO cards
Manageability
No Snapshot Backup
Backup needs to be taken at the software level (e.g. RDBMS) which should
be fast or SQL Server Always On
69
 Hardware

Database is one part of the entire system

Layer Load What? Where?
distribution

Memory &
10-20% CPU consumption Controls

Presentation
Network
communication

Memory & Compression,

5-10% CPU consumption templates
Internet Network
communication
Customer Create Production Plant
Process design/
Memory &
Service Production Order Personnel
Rep Orders

Applications /
Accept Explode Release
Reserve Build
Customer Bill-of- Production
Material Products

60-70%
Order Material Orders

CPU consumption
Schedule
Customer Part Material Production Task
Order

Customizing
Confirm
Delivery

Application Network
communication Tech.
10-20% Infrastructure/ DB
Memory & CPU
consumption, physical I/O OS
Database

Critical to optimize the entire system infrastructure

database, application servers and even clients/devices 70
 Hardware

Quanta Computer RUN SAP on SQL Server WITH FLASH MEMORY STORAGE
Single instance of SAP ERP (FI, CO, SD,
MM, PP, QM) with heavy
DB size : 7TB (Already compressed on
SQL2012 = 30 TB on uncompressed
Oracle/DB2)
IT/System Log file (1TB) Log file (1TB)
Admin 500k IOPS
Synchronous Replica,
500k IOPS

AP + DB = 280k SAPS Automatic Failover capability

64 core, 1TB RAM, 64 core, 1TB RAM,

10TB SSD Storage 10TB SSD Storage
SAP SAP ERP DB
ERP DB Replica

SAP DB Database file

SAP DB Database file SAP
(7TB) (7TB) Application
Server 2 Million IOPS Server 2 Million IOPS
Server

End user/Business
71
 Hardware

NEC Fielding Performance Boost with

Flash Memory Storage

Moving to SQL Server SSD Appliance

with 80-core, 2TB RAM and 16TB
Flash Memory Storage
Dramatically stabilizing both batch and
10 x Application NEC Storage
online performance of SAP CRM/ERP
servers (backup)
During monthly closing or fiscal year (7 x dialog, 3 x
end the system used to get quite busy batch)
batch jobs got delayed and needed to
be killed over and over again - which
sacrificed business productivity (esp.
FC
CRM) Switch
FC SAP
Database access time 100 times Switch ERP
faster SAP
The previous infrastructure could CRM
handle up to 30 jobs in parallel -> Now
2 x NEC Express Violin Memory 6000 Series
up to 70 jobs 5800 16TB
Batch jobs now running automatically 80 CPU core, 2TB (Flash
SQL Memory
Server SSDStorage)
without manual interventions by RAM
Appliance 72
operators
 Hyper-V

Windows Server 2012 R2 Hyper-V

New features for unprecedented virtualization of SAP workloads :

- 64-node cluster running up to 4000 VMs

- 64 logical CPUs inside a single VM
- 1TB memory in a single VM
- Many improvements in the areas of network and storage
- Live and storage migration much faster than before
- Script everything via PowerShell
- Hyper-V replication for DR cases
- Online VSS backups of VMs
- Deployment guide for SAP on Hyper-V released on our blog
- Fully features Cluster File System
Details :
http://technet.microsoft.com/en-us/library/hh831410.aspx
http://technet.microsoft.com/en-us/windowsserver/hh968267.aspx
http://www.microsoft.com/en-us/server-cloud/windows-server/server-virtualization.aspx 73
 Hyper-V

SAP ON HYPER-V VIRTUAL MACHINE

SIZING DB size
(after full SAP DB TempDB # of
page GB layout (per layout (per LUN (per ABAP PHYS-
# of SAP compression 2 tier or vCPU RAM Networ SQL SQL SQL insta MEMSIZ
Size users ) 3 tier ? for VM for VM k instance) instance) instance) nces E
4 x 1GB 5x
DB and AP Single 4 datafiles, datafiles, 50-80GB
Small 150 or less 320GB or less together 4 32 10Gb 1 x 40GB log 1 x 1GB log LUN 2 16000
5x
4 x 1GB 100-
320GB - DB and AP Dual 8 datafiles, datafiles, 140GB 24000-
Medium 150 to 500 640GB together 8 128 10Gb 1 x 80GB log 1 x 1GB log LUN 4 to 6 32000
5x
16 datafiles, 4x 1GB 100-
500 to DB and AP Dual 1 x 200GB datafiles, 200GB 8 to 16000-
Large 5000 640GB - 1TB separate 16 192-384 10Gb log 1 x 1GB log LUN 10 24000
8x
100-
200GB
LUN,
X-Large 1 x Log
(SQL 16 datafiles, 4x 1GB LUN
Server DB and AP 384- Dual 1 x 600GB datafiles, should be
Only) - 1TB or more separate 32-64 1024 10Gb log 1 x 1GB log 1TB - -

74
 Hyper-V

Hyper-V - Scalability

75
 Hyper-V

Hyper-V - Scalabilty

76
 Hyper-V

Hyper-V 3.0

Guest operating system (server)

Maximum number of Maximum number
virtual processors Guest operating system (client)
of virtual processors
Windows Server 2012 64 Windows 8 32
Windows Server 2008 R2 with Service Pack 1 (SP
64
1) Windows 7 with Service Pack 1 (SP 1) 4

Windows Server 2008 R2 64

Windows 7 4
Windows Server 2008 with Service Pack 2 (SP 2) 8

Windows Vista with Service Pack 2 (SP2) 2

Windows Home Server 2011 4

Essentials edition - 2 Windows XP with Service Pack 3 (SP3) 2

Windows Small Business Server 2011 Windows XP x64 Edition with Service Pack 2
Standard edition - 4 2
Windows Server 2003 R2 with Service Pack 2
(SP 2)
2
(SP2) CentOS 5.7 and 5.8 64

Windows Server 2003 with Service Pack 2 2 CentOS 6.0 6.3 64

CentOS 5.7 and 5.8 64 Red Hat Enterprise Linux 5.7 and 5.8 64
CentOS 6.0 6.3 64 Red Hat Enterprise Linux 5.9 64
Red Hat Enterprise Linux 5.7 and 5.8 64 Red Hat Enterprise Linux 6.0 6.3 64
Red Hat Enterprise Linux 5.9 64
SUSE Linux Enterprise Server 11 SP2 64
Red Hat Enterprise Linux 6.0 6.3 64

SUSE Linux Enterprise Server 11 SP2 64 Open SUSE 12.1 64

Open SUSE 12.1 64 Ubuntu 12.04 64

Ubuntu 12.04 64

77
 Hyper-V

Virtualization and SAP

1409608 - Virtualization on Windows

Supported platforms: Hyper-V, VMware, INxHY

1409604 - Virtualization on Windows: Enhanced moni

toring
Necessary to configure hypervisor security for SAPHostExec monitoring
Powershell script via http://blogs.msdn.com/b/saponsqlserver soon available for Hyper-V
parent partition configuration
1492000 - General Support Statement for Virtual En
vironments
1570141 - Key Figures of Virtualization on Hyper-V
1246467 - Hyper-V Configuration Guideline
1374671 - High Availability in Virtual Environment
on Windows
78
 System
Center
System Center 2012

Service Manager

Orchestrator
Service
Manage
ment

Autom Provis
ation ioning

App Controller

Config
Protec
uratio
tion
n
Endpoint protection
Monit
oring

79
 System
Center
Private Cloud : Dialog Instance Provisioning
http://blogs.msdn.com/b/saponsqlserver/archive/2012/03/19/microsoft-and-sap-netweaver-step-by-step-up-to-the-cloud-part-ii.aspx

SAP
New SAP Dialog
Instance

SAP DI

1. create SAP VM from template

2. install SAP DI on the fly via unattended
sapinst
3. domain join
4. SAP Logon Group join via connmove
Easycloud
5. Workflow control via System
Center Orchestrator 80
 System
Center
Private Cloud : Clone Sample
http://blogs.msdn.com/b/saponsqlserver/archive/2012/08/05/microsoft-and-sap-netweaver-step-by-step-up-to-the-cloud-part-iv-simple-offline-copy-of-a-central-system.aspx

SAP Source SAP System

System Clone

SAP SAP

1. create SAP VM from template

2. backup SQL Server DB ( source )
3. restore SQL Server DB ( clone )
4. SAP Rename Tool
5. post-copy tasks
6. process control via System Center Orchestrator
and
connmove Easycloud
7. self-service portal via System Center Service 81
System
Center

82
 End users
network

10Gb Ethernet 10Gb Ethernet 1Gb Ethernet

Switch Switch Switch

10Gb 10Gb
1Gb NIC 1Gb NIC
NIC NIC
VM- VM- VM- VM- VM- VM- VM-
VM-SAP- VM-SAP- 1 2 VM-SAP- 3 4 5 6 7
AP1 4cor AP2 4cor 4cor 4cor 4cor 4cor
DB 4cor
e e e e e e e
16core 8core 16core
192GB RAM 128GB RAM
30G
B
30G
B 192GB RAM
32G
BRA
32G
B
32G
B
32G
B
32G
B
****
RAM M RAM RAM RAM RAM
(L) (M) RAM (L) (S) (S)
(S) (S) (S) (S) (S)

16-core, 8Gb FC/HBA 8Gb FC/HBA 8Gb FC/HBA 8Gb FC/HBA 16-core,
384GB RAM 384GB RAM

FC SAN Switch FC SAN Switch

LUN1 LUN5
LUN2 LUN3 LUN4
for SAP for SAP
for SAP for SAP for SAP
DB T-log,
DB DB DB
files Tempd
files files files
b

LUN10 LUN11 LUN12 LUN13 LUN14 LUN15 LUN16 LUN17 LUN18 LUN19
for for for for for for for for for for
SAP- SAP- SAP- VM1 VM2 VM3 VM4 VM5 VM6 VM7
DB OS AP1 OS AP2 OS OS OS OS OS OS OS OS
83
 FC SAN Switch FC SAN Switch

LUN1 LUN5
LUN2 LUN3 LUN4
for SAP for SAP
for SAP for SAP for SAP
DB T-log,
DB DB DB
files Tempd
files files files
b

LUN10 LUN11 LUN12 LUN13 LUN14 LUN15 LUN16 LUN17 LUN18 LUN19
for for for for for for for for for for
SAP- SAP- SAP- VM1 VM2 VM3 VM4 VM5 VM6 VM7
DB OS AP1 OS AP2 OS OS OS OS OS OS OS OS

: 300GB Spindle (15krpm,

150IOPS/spindle)
LUNs for Database files (e.g. 1TB after compression) LUN for Log
+ TempDB (Primary) | IOPS = 4,500 | Spindles = 30 (Primary)

Storage for primary database

84
 : 300GB Spindle (15krpm,
150IOPS/spindle)
LUNs for Database files (e.g. 1TB after compression) LUN for Log
+ TempDB (Primary) | IOPS = 4,500 | Spindles = 30 (Primary)

Storage for primary database

LUNs for Database files (e.g. 1TB after compression) LUN for Log
+ TempDB (Secondary) | IOPS = 4,500 | Spindles = 30 (Secondary)

LUN for backup of Database

files (e.g. 800GB) + log |
Spindles = 10

| Storage for secondary

database 85
Agenda

Topic Time
Summary of the past SAP discussions between Kwik and
1 8:00 am 8:30 am
Microsoft
8:30 am 11:00
2 SAP on SQL Server Update
am
11:00 am 12:00
3 SAP on Windows Server / Infrastructure Update
pm
4 SAP Platform Migration 1:00 pm 3:30 pm

5 SAP and Microsoft Business Intelligence and SharePoint 3:30 pm 4:00 pm

6 Summary and Next Step 4:00 pm 4:30 pm

86
 Migration Project Overview

Installation of
DB software
SAP software Installation of
Export / Import DB software
SAP software
Preparation Export / Import

1.Test Migr. 2.Test Migr.

HW Partner Export / Import
Sizing Switch over to
HW Order
Test Phase new landscape
Migration Partner
Staffing
Project planning
SAP contracts Technical Tests Final Migr.
Basis functionality, Performance
Printing, 3rd party tools
Application Tests
Key user test Support during
Data consistency Support
first days
Trainee of the SAP Basis team Optimization

Timeline (typically 3 to 9 months)

87
 Technical Migration Process - Overview

SAP SAP

UNIX
UNIX Windows
Windows
Oracle
Oracle SQL Server
SQL Server

R3load R3load
DBSL DBSL
Read Read

Write Write
D:\Export_Data\

Dump Files
app. 10% of DB size
88
 Migration Process Classic approach

Downtime
Preparations
Shutdown of the SAP
system (Log of users)
R3load
R3load
R3load
R3load
R3load
R3load
R3load Transfer R3load
R3load
R3load
R3load
R3load Startup
R3load the
system
R3load Post activities

Friday, Time Monday,

6 pm 6 am 89
 Optimization Reduce Downtime

Splitting
Split Tabart in smaller packages
Split tables in smaller pieces (> 6.20)

Usage of Migration Monitor

Data will be already imported, while export is still running

Unsorted export of data possible

Use of application servers for R3load processes
VLDB (very large databases):
IMIG (Incremental Migration), still on project basis
90
 Migration Process Optimized approach

Downtime Saved time

Preparations
Shutdown of the SAP
system (Log of users)
R3load R3load
R3load R3load
R3load R3load
R3load R3load
R3load R3load
R3load R3load
R3load R3load
R3load R3load
R3load R3load
R3load R3load
Startup
the
R3load R3load
system
Post activities

Friday, Time Monday,

6 pm 6 am 91
How to Speed Up Migration
# Where What Solution

1 Source I/O (Data Read) Table Splitting, Parallel

Export
2 DB Server Processing Power Table Splitting, Parallel
Export
3 Application Server Processing Attach Additional x86
Power Servers
4 Destination I/O (Log Write) SSD, Parallel Import

5 DB Server Processing Power Scale Up with x86

Servers
6 Application Server Processing Scale Out with x86
Power Servers
7 Network Data Transfer 10 Gbit Ethernet

92
 Risks and Issues

Missing Data or Inconsistency of the database

Duplicate Keys
Missing tables

Interfaces
Disk paths and file destinations
OS commands in the program code of the interfaces
Open SQL inside program code

Converting of Scripts
Usage of Powershell

Printing
Changing of the print server from UNIX to Windows

Third-party tools
Available on the new platform? 93
 Migration Project Overview

Installation of
DB software
SAP software Installation of
Export / Import DB software
SAP software
Preparation Export / Import

1.Test Migr. 2.Test Migr.

HW Partner Export / Import
Sizing Switch over to
HW Order
Test Phase new landscape
Migration Partner
Staffing
Project planning
SAP contracts Technical Tests Final Migr.
Basis functionality, Performance
Printing, 3rd party tools
Application Tests
Key user test Support during
Data consistency Support
first days
Trainee of the SAP Basis team Optimization

Timeline (typically 3 to 9 months)

94
URL

Blog: Running SAP Applications on SQL Server

http://blogs.msdn.com/b/saponsqlserver/
SAP Community Network SAP on SQL Server
http://www.sdn.sap.com/irj/sdn/sqlserver

95
QUESTIONS ?
1. Why is SAP platform migration safe ?
2. How to minimize the downtime of system copy ?
3. How to make the SAP platform secure ?
4. How to make the SAP platform reliable ?
5. Why Microsoft platform ?

96
Q1. Why is SAP platform migration safe ?
SAP applications are literally multi-platform
SAP system copy moves an entire SAP environment from one to another
This is an export from a SAP instance and an import to another
The interim dump file is OS/DB independent
All repositories are stored in SAP dictionary tables SAP system copy tool recognizes and deploys all
settings/ configurations in the destination
OS/DB platform in the destination can be same or different as long as its a
platform certified by SAP (e.g. Windows and SQL Server)
Homogeneous copy = Moving to the same platform
Heterogeneous copy = Moving to a different platform = SAP platform migration
SAP homogeneous copy and heterogeneous copy are the same in procedure

expor Dum impor

t p file t

97
Q1. Why is SAP platform migration safe ?
When migrating to a different OS/DB platform, changes are
quite limited
ABAP code including custom objects no need to change
Tables and indexes no need to care - SAP system copy tool copies everything
needed based on repository
DB index hints in OPENSQL no need to care simply ignored on SQL and SQL
Server optimizer engine finds good execution plans automatically
RFC/BAPI no need to change
File paths, OS commands and Printing to be reviewed anyway and should be
changed on variant settings if needed
Files format, Scripts to be confirmed
Operations no change (e.g. not necessarily need to apply monthly security
patches, index rebuild is optional)

Risks of platform migration can be calculated -

SI costs are almost the same as homogeneous copy - why hesitate ? 98
98
Q2. How to minimize the downtime of system copy ?
CPUs @ DB Power of Additional Power of CPUs @
app export app DB
Wintel
servers servers servers
DB
export import Scale
export import Up
exp imp exp imp

exp imp e i Table

split, AP
e i e i e i SSD
export/ Scale
e i for log
import in Out
Storage @ . Storage @
parallel
DB DB
# Where What Solution
1 Source I/O (Data Read) Table splitting, Parallel export
2 DB Server Processing Power Table splitting, Parallel export
3 Application Server Processing Power Attach additional Wintel Servers for export
4 Destination I/O (Log Write) SSD, Parallel import
5 DB Server Processing Power Scale up with Wintel servers
6 Application Server Processing Power Scale out with Wintel servers
7 Network Data Transfer 10 Gbit Ethernet
99
Q2. How to minimize the downtime of system copy ?

Hire a SAP certified migration consultant in

your SAP migration project
Hire an experienced SAP migration partner
if downtime-minimize is critical
Abeam Consulting - http://www.abeam.com/gbl/eng/
Realtech APAC - http://www.realtech.com/
BNW Australia - http://www.bnw.com.au/html/index.html

Repeat system copy testing and optimize

the procedure to minimize downtime
100
Q3. How As well as blocking attacks from viruses,
minimizing security patch installations
to make which should stop the SAP systems
in many cases is highly recommended
the SAP RAS Web
as a best practice

platform DMZ segment

secure ? WWW

WWW
RAS Router (External) DNS Mail VPN

RAS
Segment Firewall
-> Open only
necessary ports (* In-
bound TCP 3200,
3300, 3600, 80000)
Proxy
Corporate clients Corporate Servers
segment segment

WWW WWW
Dire
WWW ITS )
WWW EP )
File (Portal) (Portal) DNS Mail
ctory

SAP
servers
segment SAP DB BW SCM 101
Q3. How to make the SAP platform secure ?
Q: Were still worried about the security of Windows, especially virus infections. Do we
need to stop SAP servers every month for monthly security patch installations ?
Considering the workload to test/apply all of the patches that Microsoft releases would
Windows be more expensive to manage than UNIX or mainframe ?
A: Hardening has already been a very common practice for security. Hardening
includes for example - (1) blocking unnecessary network ports (traditional SAP apps use
only 4 TCP ports, TCP 3200/3300/3600/80000), (2) leaving unnecessary OS services
turned off (default settings on Windows Server), and (3) restricting unnecessary
operations like browsing, e-mailing or using Office on SAP servers. Running anti-virus
software on production SAP/DB servers is also common. Generally speaking
SAP on Windows admins should prefer other security measures than security patch
installations, which should come last. If you look through the MS monthly
vulnerabilities - you would realize security patches that need to be applied urgently
(e.g. within 24 hours) are very limited. For example vulnerabilities on IE, Office etc can
be out of scope. Assuming hardening is well designed/implemented in advance, patch
installations on SAP servers can be quite rare, probably almost zero. Microsoft published
a security whitepaper specifically for SAP/Windows environment. So far none of our
customers reported additional operational workload after migrating to Windows. BTW
beta versions of Microsofts security patches are sent to SAP AG
1 or 2 week(s) before their public release, so that SAP can conduct compatibility tests in
advance. How to test/install/uninstall patches is documented in the whitepaper. 102
Q3. How to make the SAP platform secure ?
On your critical application/database servers -
Remove or keep disabling Internet Explorer
Dont set up unnecessary client software e.g. SAP GUI, Office that should run
on a separate console PC - monitoring studio
Dont run unnecessary server software e.g. FTP, Web server that should run
on less-critical servers separately
Segregate your critical application/database servers from other
subnets
Open only necessary ports on network switch (or each host)
SAP applications requires inbound TCP ports of 3200, 3300, 3600 (instance # is
00 in this case) and 80000 (portal, configurable) only
This way your application/database servers are quite secure already
Check monthly security patches but minimize patch installations
(basically zero) Service pack installations are more preferred (e.g.
once a year)
Following best practices can make SAP on Windows quite secure
No change in administration/operation from other platforms 103
103
SAP on WINDOWS SECURITY WHITEPAPER
http://blogs.msdn.
com/b/saponsqlserv
er/archive/2012/05
/28/sap-on-sql-ser
ver-security-white
paper-released.asp
x

104
Q4. WE HAVE MANY ADD-ONS. Migration is STILL POSSIBLE ?

When migrating to a different OS/DB platform, changes are

quite limited
ABAP code including custom objects no need to change
Tables and indexes no need to care - SAP system copy tool copies everything
needed based on repository
DB index hints in OPENSQL no need to care simply ignored on SQL and SQL
Server optimizer engine finds good execution plans automatically
RFC/BAPI no need to change
File paths, OS commands and Printing to be reviewed anyway and should be
changed on variant settings if needed
Files format, Scripts to be confirmed
Operations no change (e.g. not necessarily need to apply monthly security
patches, index rebuild is optional)

Risks of platform migration can be calculated -

SI costs are almost the same as homogeneous copy - why hesitate ? 105
105
Q5. HOW SAP PLATFORM SWITCHERS MIGRATED
UNIX SHELLS ?
Q : We currently have many UNIX shell scripts, which seem a blocker
for SAP migration.

A :Every time you replace the hardware UNIX shells should be

thoroughly reviewed and rewrote anyway, even if its from UNIX to
UNIX. Even if there're thousands of UNIX shells in place, many of
them might not be used any more, plus shells for system
management can be replaced by
Windows Server's standard functionalities. If hundreds of shells are
left, you can find some specific patterns to save the dev cost. Most of
our customers which successfully completed migration to Windows,
re-wrote the functionalities with Windows Scripting Host or other
scripting technologies.
106
Q6. How to make the SAP platform RELIABLE ?
Q : We experienced unplanned shutdowns of Windows in the past, what are the key points when
using Windows Server in the LOB space ?

A : What to care are always the same whatever platform you use. The following points determine
the reliability and availability of your LOB systems.
1. 64-bit hardware and software are used ?
2. The whole set of hardware and software is strictly tested by the hardware vendor(s) in
advance ?
Especially firmware and device drivers are important
3. Any standardization of the set of hardware and software ?
4. Customer have a high availability support contract with the hardware vendor(s) ?
5. Hardware vendor(s) periodically deliver hotfix information for proactive change
management ?
Especially firmware, device drivers, OS, RDBMS, applications and anti-virus etc
Once or twice a year
6. Customer have a test environment with the same spec as the production ?
7. Customer have a rule to deploy any change on the production after internal test on the test
environment ?
8. In case of a trouble root cause analysis can be done on the test environment ?
Not the production, where recovering the services as soon as possible is more important than analysis

Golden rules for reliability are same as other platforms 107

107
Microsoft PREMIER SUPPORT SERVICE
http://www.microsoft.com/singapore/services/microsoftservices/prem.mspx

Benefits Key Features Premier Standard

Support Assistance Flexible
Proactive Services Health Check and Infrastructure Workshop Available
Global and Regional Workshops Available
Problem Resolution Support Flexible
24x7 Coverage Included
Problem Resolution Support
24x7 Critical Situation Escalation Management Included
Rapid Onsite Support Included
Proactive Information Distributiont Included
Knowledge Transfer Microsoft Premier Online Included
TechNet Plus Subscription Included
Account Representative* Shared, designated contact
Remote vs Onsite Resource partly onsite
Direct Relationship
Account Profiling and Reporting Monthly
Case Monitoring and Escalation Management 24x7

108
Microsoft PREMIER SUPPORT SERVICE
https://premier.microsoft.com/gp/PRMRSISevDetails
Severity Customers situation
Critical business impact: Customers
business has significant loss or
degradation of services
A Needs attention within 1 hour
Submissio
n by (*) Severity A support is not available
phone for incidents submitted over the Web.
only For Severity A support, please contact
Microsoft using the phone number for
your region available on the
Contact Page.
Moderate business impact: Customers
business has moderate loss or
degradation of services but work can
B reasonably continue in an impaired
manner.
Needs attention within 2 business
hours (review note 1)
Minimum business impact: Customers
business is substantially functioning
with minor or no impediments of
C 109
services.
Expected Microsoft
Expected Customer Response
Response
First call response in Allocation of appropriate
1 hour or less resources to sustain continuous
Microsoft Resources at effort all day, every day (review
customer site as note 2)
required. Rapid access and response from
Continuous effort all change control authority
day, every day Management notification
Notification of Senior
Managers at Microsoft
Initial Response Allocation of appropriate
within 2 hours of case resources to sustain continuous
creation effort unless customer requests
24x7 continuous effort to opt-out of 24x7
unless customer Rapid access and response from
requests to opt-out change control authority
First call response in Accurate contact information on
4 hours or less case owner
Effort during business Responsive
hours only (review note
 MICROSOFT Product LIFE CYCLE Min 10 YEARS
http://support.microsoft.com/lifecycle/search/default.aspx

Extended Support End Date

# Product name (MM/DD/YY)
1 Windows Server 2012/2012 R2 1/10/2023
2 Windows Server 2008/2008 R2 1/14/2020
3 Windows Server 2003/2003 R2 7/14/2015
4 Windows 2000 7/13/2010
5 Hyper-V 3.0 1/10/2023
6 Hyper-V 2.0 1/14/2020
7 Virtual Server 2005 1/13/2015
8 Windows 8/8.1 1/10/2023
9 Windows 7 1/14/2020
10 Windows Vista 4/11/2017
11 Windows XP 4/8/2014
12 SQL Server 2014 7/9/2024
13 SQL Server 2012 7/12/2022
14 SQL Server 2008/2008 R2 7/9/2019
15 SQL Server 2005 4/12/2016
16 SQL Server 2000 4/9/2013
17 Visual Studio 2012 1/10/2023
18 Visual Studio 2010 9/8/2020
19 Visual Studio 2008 4/10/2018
20 Visual Studio 2005 4/12/2016
21 Visual Studio .NET 2003 10/8/2013
22 Visual Studio .NET 2002 7/14/2009
23 System Center 2012/2012 R2 7/12/2022
24 Microsoft JDBC Driver 4.0 for SQL Server 3/6/2017 110
 Simplifying SAP Infrastructure
Legacy & Complicated Modernized & Simplified
SAP App SAP
Patterns and
? Database Microsoft practices
to run SAP
? OS Microsoft applications
available in
? Monitoring, backup,
Scheduler and security Microsoft market
Microsof
? Virtual Machine
t
Microsof Successful deployment
? Server Any t guaranteed
(Azure
? Storage Any
)
? Network Any
111
Thank you.

112