November 5, 2016 at 8:34 am
I'm familiar with partitioning a result set using the OVER(PARTITION BY.....) option. However, I'm reading a study kit by Itzik Ben-Gan, and he writes about partitioning views and references partitioning tables. However, there isn't really a clear explanation of what a partitioned table actually is. Is it just simply the result set partition I am already familiar with? To me, a table that's already partitioned doesn't make sense because tables are relational and thus have no order, therefore a partition isn't really useable... then again, I am new at this.
Thanks!
November 5, 2016 at 11:25 am
scarr030 (11/5/2016)
I'm familiar with partitioning a result set using the OVER(PARTITION BY.....) option. However, I'm reading a study kit by Itzik Ben-Gan, and he writes about partitioning views and references partitioning tables. However, there isn't really a clear explanation of what a partitioned table actually is. Is it just simply the result set partition I am already familiar with? To me, a table that's already partitioned doesn't make sense because tables are relational and thus have no order, therefore a partition isn't really useable... then again, I am new at this.Thanks!
Unfortunately, study kits frequently aren't for newbies and they usually say so right in the book. That, notwithstanding, Yabingooglehoo is your friend here.
https://www.google.com/?gws_rd=ssl#q=partitioned+tables+sql+server
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2016 at 5:33 pm
A partitioned table actually is a split of a table into sections. Right now, your tables are really set as pages, and you treat the table as one object. You can split this with a partition key and deal with sections of the tables.
Here's a basic BOL page: https://msdn.microsoft.com/en-us/library/ms188730.aspx
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply