Skip to Content
0

BOBI 4.2 installation on ASE 15.7 with 16K pages

Oct 14, 2016 at 11:55 AM

128

avatar image
Former Member

The SAP installation guide for BOBI 4.2 speaks of creating a DB with page size of 8KB for the optimal performance of CMS; however we have a DEV tier setup where the BOBI 4.2 instance was installed on ASE DB with 16K pages. The independent DB server hosts a 32GB RAM with the expected DB size of not more than 100GB, at present. So, is it ok to keep 16K pages in ASE DB under the current circumstances ? Is the ASE DB performance better with 8K pages ? Thanks.

Reference:

https://websmp203.sap-ag.de/~sapidp/012002523100003123382016E/sbo42sp2_bip_inst_unix_en.pdf

Section : 4.2.2 Extra requirements for Sybase ASE

10 |10000 characters needed characters left characters exceeded

that is what your tests should show, there is no one answer to this.
our testing had shown good results with 8Kb. how your particular DB performs depends on many factors, page size is only one of them.
Work with your DBA to profile its performance.

0
Former Member
Denis Konovalov

Sure Denis. Thanks. I guess Mr.Mark gives a clear picture to me for now.

0
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Mark A Parsons Oct 14, 2016 at 02:09 PM
1

NOTE: I don't work with SAP applications. I do work with SAP/Sybase ASE. So fwiw ...

-----

As Denis has already touched on, 'better' performance is based on a slew of factors ... dataserver configurations, type/speed of disks, amount of memory, database/application/query design, etc, etc, etc. Larger pagesizes typically provide a performance improvement in environments where you have to rely on pulling large volumes of data from disk on a regular basis.

-----

As for whether to use 8K or 16K ... one key item to keep in mind ...

You cannot dump-and-load databases between dataservers that have different pagesizes (eg, you cannot dump a 16K pagesize database and load it into a 8K pagesize database, and vice versa). So, when planning on what pagesize to use for a new dataserver, make sure you use the same pagesize for all dataservers where you will need to be able to dump-and-load databases (eg, dump database from production dataserver, load into database on dev/test/QA dataservers).

Most companies tend to pick one pagesize for all dataservers (eg, SAP tends to recommend 16K most of the time for their applications).

If you ever have to move a database between dataservers with different pagesizes ... it's a very time-consuming process (eg, ddlgen tables/procs/triggers/indexes/permissions, bcp data out/in, create/load procs/triggers/indexes/permissions, update stats, etc).

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Mark,

Thanks for the insight.

0
Bharath B N
Apr 09 at 05:29 PM
0
Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Apr 09 at 02:56 PM
0

Hi,

The link is not working anymore.

Thanks,

Aravin

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Apr 11 at 02:00 PM
0

Thank you Bharath B N

Share
10 |10000 characters needed characters left characters exceeded