Hi, I am a developer and would need some DBA-advices.
We are starting to get performance problem with a MSSQL2005 database. The visible effects of the incidents is mainly CPU-hog on the server but operations reported that it was also draining resources from the SAN (not always). the main source of issues is for sure in some application but I am wondering if we should partition some of the main tables anyway in order to relax the I/O pressure.
The base is about 60GB in one file.
The main table (order) has 2.1 Million rows with a 215 colones (but none is huge).
We have an integer as PK so it should be OK to define a partition function.

Will we win something with partitioning? will partition indexes buy us something?
Here are some more facts about the DB and the table

database_name  database_size    unallocated space
My_base         57173.06 MB     79.74 MB
reserved        data            index_size      unused
29 444 808 KB   26 577 320 KB   2 845 232 KB    22 256 KB

name        rows            reserved    data        index_size      unused
Order   2 097 626       4 403 832 KB    2 756 064 KB    1 646 080 KB    1688 KB

Thanks for any advice

Dom