Documentation on storage policies use the term "TABLE" - but I thought TABLE was only a logical construct, with PROJECTION(s) being the objects that are actually stored and physically created. So when you create an object-level storage policy is it really at the TABLE level, or the PROJECTION level? If it is indeed the TABLE level, does that mean that the policy is applied to ALL PROJECTIONS which are associated with that table?
storage policies - do they relate to TABLES or PROJECTIONS?
This is table level, when you load that on a table, it would go to all the projections associated with it to the storage policy assigned to the table.
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
