so you have already partitioned the table in your database and now you are concerned with the performance issues.
If a table is partitioned, SQL Server can often eliminate irrelevant partitions from even being considered by query optimizer and only examine those partitions that contain the requested data, as defined by query predicates. This feature is called partition elimination. In order to benefit from partition elimination, the query should not return data from all partitions.
it was general description, what sort of help you want, will you please elaborate ?
if this has helped you out . please let me known and suggestions are most welcome.
Yes.. I have partitioned the existing table. Now I face performance issue .
Stored procedure is for selecting the data...
After parationing, any change can made in the stored procedure for selecting data .Any alternative ?
Any other method for partitioning method for existing table , not a new table
Certainly, the most important point of partitioning is speed.
check out if the query is hitting all the partitions ?
is yes then,you can slightly modify your WHERE clause in select argument to allow data to be selected from fact table or partition ( and not from dimension table,if fetching data from two tables) so that execution plan for the statement will not examine all the partitions.
in the same way,if you join multiple partitioned tables and specify search arguments for each table in the WHERE clause, SQL Server can eliminate partitions from each affected table and can provide excellent querying performance. The query execution plan would show multiple constant scan operators, each referencing only those partitions relevant for the given query.