A Practical Hardware Sizing Guide for Sybase IQ
A Practical Hardware Sizing Guide for Sybase IQ
A Practical Hardware Sizing Guide for Sybase IQ
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
that are undergoing constant data refreshes, however, it is quite possible to architect a system<br />
where there are two or more write nodes whose sole responsibility is to handle data changes<br />
while N number of other nodes are defined as query, or read, nodes to handle all read operations<br />
in the database.<br />
Other Features of Note<br />
Partitioning was also introduced in <strong>IQ</strong> 15. From a sizing perspective, however, this does not<br />
come in to the equation other than how it pertains to multiple dbspaces and partition placement.<br />
In order to handle tiered storage, partitioning, and object placement on disk, <strong>Sybase</strong> <strong>IQ</strong> 15<br />
introduced multiple dbspaces. The DBA can create any number of dbspaces to hold data objects.<br />
These objects include tables, columns, indexes, and partitions. The storage sizing guidelines<br />
contained in this document cover sizing of an individual dbspace, not all dbspaces <strong>for</strong> the<br />
database.<br />
Final<br />
5