SQL indexes on a large table: some large indexes or more smaller indexes?
I have a table with +/- 80 million rows (partitioned).

The inserts are getting kinda slow (about 1-3 sec). 
The query plan says 68% of the insert is `clustered index insert`, but there are also some triggers on the table for every insert / update and delete. So its kinda hard to say what is really causing the time.

Anyways, we have some indexes on that table, some with 3-5 columns in it.

What I want to know is what is better, performance wise:
To have some indexes with multiple columns in it, or to have more smaller indexes with less columns? 

All tips and suggestions are welcome.

SQL indexes on a large table: some large indexes or more smaller indexes?
===

I have a table with +/- 80 million rows (partitioned).

The inserts are getting kinda slow (about 1-3 sec). 
The query plan says 68% of the insert is `clustered index insert`, but there are also some triggers on the table for every insert / update and delete. So its kinda hard to say what is really causing the time.

Anyways, we have some indexes on that table, some with 3-5 columns in it.

What I want to know is what is better, performance wise:
To have some indexes with multiple columns in it, or to have more smaller indexes with less columns? 

All tips and suggestions are welcome.
