This is not opinion based, there is a very real way to deal with Page Files on SQL Servers.
should I really disable the page file?
and reduce it to 8 GB?
I would start at 8 GB and monitor
Paging File\% Usage Peak. If it starts going higher than 75% you may want to increase the size. Having said that I would highly question why that much of a page file would be used on a properly configured SQL Server.
The paging file(s) are used by Windows to a certain extent even when there is no paging going on. This is how the VMM (Virtual Memory Manager) works (not getting into details). There will always be a super small usage of it, so don't turn it off.
The only major times the paging file is needed is either when we have to swap (page) memory (which would mean your server is under memory pressure) or when there is a bugcheck (commonly known as blue screen of death). If a bugcheck occurs and the server is set to kernel dumps, this will be fairly small - about 2 GB of the page file will be needed. If, however, it's set to do a full memory dump then the size of the paging file will need to be the size of memory. Obviously on an extremely large server having a paging file of 2 TB+ is not going to really help for this situation. Additionally the space required for these may change between versions of windows.
There is an official KB for this: https://support.microsoft.com/en-us/kb/2860880
So... what should you set it to? I'd start at the 8 GB and go from there. Does it take some admin overhead to check every quarter, etc.? Yes, but you'll end up saving yourself a ton of wasted disk space. You could go system managed size, but again, this changes between versions of Windows and crash dump settings... plus a properly configured and sized SQL Server shouldn't have any memory pressure (externally).