Extends happen only in variable extents, and only when there are no more free blocks available in the file for space allocation and the storage engine needs to request more disk space to increase the size of the file.
Sorry for not being clear.
My assumption;
the whole point of doing this exercise is to have a pre-grown db that is logically empty. Let's consider an example, we have an AREA with variable extent that will have a table which is 30 GB (121229599 Records). As part of our exercise;
1. Let's say I ran the ST file and got this area created
2. Execute the DF and got the table created in this area
3. Load the data twice to make the table size close to 50 to 60 GB (though its not advisable, let's think i am doing this for just an understanding purpose)
4. I am applying the empty8 on to the db (which will wipe the schema and resets HWM).
My assumption is the file size will still be 50 to 60 GB.
5. Load the DF and get the table created again on this area
6. Load the data file (once this time). HWM will move accordingly.
BUT free blocks will be available till 50 to 60 GB and only when it reaches this limit the storage engine is going to request more disk space. This way performance will increase as we are loading the data to a pre-grown db which is logically empty.
I have highlighted my assumptions. Is my understanding right? If not please let me know what is helping out in gaining the performance in this exercise.