SQL and Multiple Indexes
Just having the table definition and a few rough examples is probably not enough information to get you the answer you want. You need to know which queries are going to be the most heavily used. 

For example, you only get 1 clustered index, and that's the most powerful index, so you only have one option for that. 

Are all/most of your queries likely to have a particular column (i?) involved? Do you join to other tables? On a common column? That would lead me to think i should be the first column in the clustered index. The subsequent columns in that index, should be the next most-commonly used columns (taking cardinality into consideration). You can put all the columns in the clustered index if you like, as that's effectively the order the data is stored in. So the order of the columns is NB. 

Then, single column indexes can reference the clustered index, so that helps. But your choice of those non-clustered indexes and the number/order of columns also depends on the expected usage.

Also, is this a data entry or reporting table? Data entry = more indexes make it slower to enter data. Reporting = index the hell out of it, if needed!