I recently added more CPU cores to a SQL Server and as best practices advise, I separated out the tempDB files into the same number of cores(8).
Also along with best practices, I expanded the size of the new tempdb files, limited auto-growth and shrunk the original files to match the size of the new files.
The problem is, since I was going from a single core to 8 cores, all of the tempdb data remained in the first file, which wouldn't allow me to shrink. Now I have one tempdb file that is larger than the others and I would like to change that.
I suspect to fix this it will require an outage.
Is there a way to do this without an outage?
Is this problem even worth addressing? I know what best practices say, but does this instance really cause any practical problems other than ugliness?