Table Partitioning - SQL Tuning/Performance
Has anyone used SQL table partitioning on large records in PSFT and what kind of results have they found? What kind of performance benefits or issues does it raise with access the data? Is there any impact the PSFT UI? Any other tips, recommendations?
IE: we have several large records including PS_COMBO_DATA_TBL & PS_PTAFAW_STEPINST which contain several million rows of data and while we've done the standard work of SQL tuning, adding indexes, etc, we'd still like to improve the performance of these records especially when they're being referenced so often by the system.
We're taking a look at SQL table partitioning, but just aren't that familiar with it.
IE: we have several large records including PS_COMBO_DATA_TBL & PS_PTAFAW_STEPINST which contain several million rows of data and while we've done the standard work of SQL tuning, adding indexes, etc, we'd still like to improve the performance of these records especially when they're being referenced so often by the system.
We're taking a look at SQL table partitioning, but just aren't that familiar with it.
0