SAP ASE synchronizes a portion of the data and log segments synchronously before making the database available, allowing the initializer to work ahead of any commands that require space in the database.
However, you may occasionally see a performance impact to commands normally run against the database while SAP ASE is busy initializing the space. This occurs because a command that requires space that is not yet initialized must initialize the space before it proceeds.
Information about initialized space is stored in sysattributes.
select lstart=object_info1, size=object_info2, segmap=object_info3
from master..sysattributes where class=42 and object=db_id("mydb")
lstart size segmap ----------- ----------- ----------- 1536 3584000 3 5120 51200 4
If the query returns one or more rows, the database contains space not yet initialized (in this query, the mydb database). This query does not indicate if the asynchronous initialization service task is running, only that it is not finished (if it was finished, the result set would contain zero rows).
select spid from sysprocesses
where dbid=db_id("test") and cmd="CRDB AUINIT"
spid ------ 22
Asynchronous initialization of database 'database_name' has completed.
Asynchronous database initialization terminated prematurely for database '%.*s'. Use DBCC DBREPAIR(%.*s, async_database_init, start) to restart it if required as uninitialized pages will incur a small performance penalty when they are first referenced.