No. You will have to partition the respective child or reference tables as well and make sure the data references are intact across partitions on both parent and child tables to avoid integrity issues later when you switch out data from parent tables.
FYI, the primary goal of partitioning is ease of data management not performance. Though it may improve performance it is not meant to be used as a performance tuning technique.
Sidd DBA, I disagree with your statement. If the primary goal was just for ease of data management, you don’t need to partition. You could simply denormalize table and eliminate joins. The idea behind partitioning IS TO improve query performance and you do so by splitting larger data into multiple file groups to reduce the number of rows a query has to process. FYI, it may serve you best to further your studies before throwing an uneducated statement. :)
@@nismokid I'd suggest you to do a bit research before posting generic statements. The primary purpose of Table partitioning is not improving query performance. Better you start reading and doing research.
I have 3 tables with ralational A to B to C and A B having datetime column but C having only Interger column, If i want to create Partioning how can do on these 3 tables. If do on A table it will reflcet in all the tables with partitoning
The tutorial is not bad, but to be honest I started to stop to watch because you take too much time to explain basic concepts, and because of this my attention went down a bit. You should be more straight-forward with your video man. Take it as an humble suggestion.
