Validation of Partitioned table Performance We are testing partitioning on a table which contains a datetime column (DateColumn).

Partition function I am using is:

-- 138623  +  16774 records
CREATE PARTITION FUNCTION pf_TableName_DateColumn (datetime)
AS RANGE LEFT 
FOR VALUES ('20160101', '99991231');



How do I verify that partitioning the table is improving query performance?  
There is one Clustered index on PARTITION SCHEME, do remaining non clustered indexes get statistics of partition?


I am testing it by running the same stored procedure with date parameters on two databases (real and replica). One contains a partitioned table (two partitions) whereas the other is simple. Profiler doesn't show any difference in CPU, Duration, Rows, or Reads.
Why would you expect performance to be different with partitioning? Partitioning improves manageability but performance depends greatly on the workload and queries.  For example, if you have a useful index on the DateColumn, you will likely get the same performance with and without partitioning.  With no index on the column, performance may be better with partitioning as long as only the needed partitions are scanned due to elimination.  But if an index can prevent the scan, that would provide the greatest performance benefit.