MS SQL Server 2008 Optimization

Full Text Index:

For a full-text index, you must have a catalog in the database to store the full-text index. Full-text indexes cannot be placed anywhere except in full-text catalogs. Therefore, full-text catalogs must exist. Only one full-text index can be created per table or indexed view. An indexed view can only be created if it the view is created with the schehabinding option. A full-text catalog can hold multiple full-text indexes. It is highly recommended that tables and full-text indexes refer to the same full-text catalog. There can be multiple full-text indexes per database because a database can have multiple tables, and each table can have maximum of one full-text index. Therefore, each database is capable of having as many full-text indexes as the number of tables it contains.

DB Fine Tuning:

you should set the trace flag 3226. When you add this flag, it has the following effects:
Successful backup entries are not added to the SQL Server error logs. Entries are prohibited from being logged in the System event log. Only failed backup event entries are logged.
No successful backup entries are logged. You should ensure that no script is dependent on any successful backup entries that are logged either in the error log or in the System event log. A trace flag can be either
specific to a session or a global trace flag. A trace flag can be switched on or off by using the dbcc traceon and dbcc traceoff commands.

DB Compression:

SQL Server 2008 supports compression at row-level and page-level for both tables and indexes. You can use the create table and create index statements to create compressed tables and indexes. To modify the compression state of an existing table, index, or partition, you can use the alter table or alter index statements. However, configuring row and page compression can affect the performance of your sever.
When you configure row and page compression, CPU utilization is increased, while I/O utilization and memory utilization are decreased.