SQL Server has partitioning on a single column only. (Well, if you wanted to partition on a two-column combo, you could possibly partition on a computed column that covers both column, but it does not strike to me as a bad idea.)
Also beware that features like this may work considerably different on different products, so what maybe was a good idea on Oracle, may not be a good idea on SQL Server.
Exactly what do you hope to achieve with your partitioning?