Skip to Content

Customers may decide to migrate their test and/or development system MSSQL database from enterprise edition to standard edition running under SAP applications in order to provide cost efficiency.

At this stage, there is an outstanding issue need to be taken into account that MSSQL standard edition does not support on production environment. It is clearly pointed over the OSS note “62988 – Service packs for MS SQL Server” that standard edition does not support on productive systems.

From technical point of view the major problem; the consultant will face with during the database migration; converting supported functionalities on MSSQL enterprise edition, but not support over MSSQL standard edition. Find the foremost functionalities, below;

  • Parallelization
  • Data compression
  • Table/index partitioning

Degree of Parallelism and parallel index operations will not be able to support on MSSQL standard edition. Thus, it is not able to execute parallel query over the SAP system. Because of this it is inevitable to face with performance problems during the ABAP report and application processing.

Page compression and row compression functionalities does not support on MSSQL standard edition. Because of this reason it is easy to figure out the database running on standard edition is tended to grow faster than enterprise edition. As an additional side effect; growing number of block needs to be read by the database engine during the query execution. Because, uncompressed data require to read more data block than compressed which leads performance degradation over the SAP applications.

Because of table and index partitioning does not support on standard edition, BW functionalities will not be provide on SAP applications. Thus flexible Bex query reporting functionality will not be able to use, either.

Heterogeneous system copy needs to be run in order to migrate SAP system running on MSSQL standard database. Find the solutions below in order to run SAP system on MSSQL standard edition;


Data compression:

Replace &compression_page& with &compression_none& on DDLMSS.TPL file.

cretab: CREATE TABLE &tab_name&

( /{ &fld_name& &fld_desc& /-, /} ) &compression_none&

creind: CREATE &unique& INDEX &ind_name&

ON &tab_name&

( /{ &fld_name& /-, /} ) &compression_none&

Table/index partitioning:

Table and index partitioning SQL statements needs to be dropped on DFACT.SQL file. Please find the sample statements, below;

CREATE PARTITION FUNCTION

CREATE PARTITION SCHEME

Additionally, DATA_COMPRESSION value should be set “NONE”.

Parallelization:

There is no additional effort about this function. Because of standard edition does not support parallelization, even the SQL statements have MAXDOP will not be processed in parallel session.

Orkun Gedik

SDN 2012 Database and OS Platforms Topic Leader

SDN 2013 SAP on Oracle Topic Leader

KoçSistem SAP Technology Principal Consultant

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply