|
Document:
The general rule with regards to the engine page size/database page size relationship in SQL Anywhere is:
The database engine must have a page size which is greater than or equal to the maximum of the page sizes of all databases which are in use by this engine.
If the database(s) is(are) started at the same time as the database engine then the engine page size is set up correctly, according to this rule. If however, the user attempts to dynamically start another database with page size greater than the largest database page size running on the engine, the error message "page size too big" appears.
By default, database is created with a page size of 1024 bytes and, when not contradicts with the above rule, the engine is started with 1024 bytes page size as well.
Refined Solution 1
When it is possible beforehand to determine which databases will be running under a particular database engine(standalone or server), the page size of the engine should be set as the maximum page size of these databases.
Example:
Assume that there are only three database files: db1.db, db2.db and db3.db with page sizes 1024, 1024 and 2048 respectively, reside on a drive C: on a particular server. Then any of the following will set up the correct page size for database engine (server engine) named db1 :
dbsrv50 c:\db1.db c:\db2.db c:\db3.db
dbsrv50 -gp 2048 c:\db1.db c:\db2.db c:\db3.db
dbsrv50 -gp 2048 -n db1
dbsrv50 -n db1 c:\db3.db
The dbinfo.exe utility can be used to verify database page size, ie. dbinfo c:\db1.db
Refined Solution 2
Changing the page size of the databases. It can be achieved by creating a new database with a fixed page size, unloading the original database and reload it to the new database with the fixed page size.
Example:
Assume that there are only three database files: db1.db, db2.db and db3.db with page sizes 1024, 1024 and 2048 respectively, reside on a drive C: on a particular server and for a particular reason it is desired to have them have the same page size 2048 bytes each. The db3.db can be left as is, and for each db1.db and db2.db the following can be done, assuming c:\unload exists:
dbinit -p 2048 c:\db1new.db
dbunload -c "uid=...;pwd=...;dbf=c:\db1.db" -r c:\unload\reload.sql c:\unload
isql -c "uid=dba;pwd=sql;dbf=c:\db1new.db" read c:\unload\reload.sql
Performance Issue
At most one database page can be put into one engine page. Thus if you start two databases, one with a page size of 1K and one with a page size of 4K, the engine will use 4K page size, which means that the 1K page size database pages are only one quarter full. In the case of a 512 byte page size database, at least half of all cache pages will be wasted. This makes the use of 512 byte page size for databases not recommended, although it is still supported
[网页制作]CSS:font-size-adjust [网页制作]CSS:font-size
[SyBase]使用dbcc memusage确定procedure cache size大小 [SyBase]dbcc memusage确定Procedure Cache Size
[ORACLE]在Oracle9i中使用多种Block Size
| 
注：本站部分文章源于互联网，版权归原作者所有！如有侵权，请原作者与本站联系，本站将立即删除！ 本站文章除特别注明外均可转载，但需注明出处！ [MinTao学以致用网] 
