Partitioning table in SQL server is generally considered a maintenance process.
As for the column, most people I can think of use a Time based solution (Period, Year, Day) depending on data volumes.
You can place the Paritions either on seperate file groups or on the same filegroup, Seperate file groups tends to make more sense. Un- partitioned tables would ideally be left in thier own file group (Primary or others).
Once paritioned you shouldnt need to run any DBCC commands unless you are moving data and want to check the integrity afterwards.
Partitioning tables is not a performance tuning tool, work on the queries and tune them using indexes, or writing better SQL. However splitting the database into seperate file groups for Data, Indexes and binaries can help but I would suggest reading up on MS best practices for this.
_________________________________________________________________________
SSC Guide to Posting and Best Practices