To clarify, when you say "16 GB" is that the memory allocated to the resource pool or to the Server?
Does your resource pool have enough space for that 7 GB table? The OS would need at LEAST 7 GB free to hold a 7 GB table, plus space for the OS and the SQL Server Instance. OS should have at least 4 GB (based on everything I have ever read about Windows), so that leaves your SQL to hold 5 GB of that 16 in order to have space for your 7 GB table. using 100% memory is NEVER recommended as you will likely crash the OS. So, for your setup, your SQL OS is going to be using 4 GB of memory (to have 1 free) to make that work. Your queries will likley fail as SQL doesn't have enough memory to operate efficiently. I'd double that memory if you want to throw a 7 GB table at it.
Now if you have 16 GB allocated to the resource pool, do you have enough physical memory to work with that?
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.