|Bookshelf Home | Contents | Index | PDF|
A redundant array of independent disks (RAID) can provide large amounts of I/O throughput and capacity, while appearing to the operating system and RDBMS as a single large disk (or multiple disks, as desired, for manageability). The use of RAIDs can greatly simplify the database layout process by providing an abstraction layer above the physical disks, while promoting high performance.
If a RAID device is not in use, even if space is at a premium, you must separate the indexes whose names end with _P1 from the tables on which they are created. These tables are heavily used in join operations.
If you will make frequent use of Siebel Enterprise Integration Manager (EIM), you may want to put the interface tables and indexes (names starting with EIM_) on different devices from the Siebel base tables. Both tables are accessed simultaneously during EIM operations.
Table 12 describes a sample disk layout for a server dedicated to Microsoft SQL Server, where the database uses a single filegroup residing on a disk array. The use of a single RAID array for the database devices provides satisfactory performance in many cases without the administrative overhead of using individual filegroups.
If your Enterprise requires the highest performance standards, you should place heavily used tables and their corresponding indexes, such as those listed under Sizing the Database for a Siebel Deployment in a specific SQL server filegroup within your database. By creating a filegroup on a specific disk or on multiple disks, you can control where tables and indexes in your database are physically located. For a discussion of this, see Database Physical Device Planning.
Your choice to use RAID devices or multiple filegroups to distribute database objects depends solely on how great your performance needs are. It is recommended that you work with your hardware vendor to determine the optimal RAID configuration for your specific requirements.
|Deployment Planning Guide|