What you show in that picture is a private key in hexadecimal format, but it has nothing to do with SHA256 or any hash function. (Hash function output is usually represented as hex, but just because something is in hex does not mean it is the output of a hash function). What you want to do is take a private key encoded in hex, and re-encode it in WIF in both compressed and non-compressed mode. I'm not sure why you would want 1,996,000 Bitcoin addresses, half made from compressed keys and half not, but it's unlikely that anybody has made a script to do this. It could be done though.

I should stress that if for whatever reason wherever you got this data from was public, or you could believe that there's even a small chance that someone else would have access to the same list of hex data you have, that using that data as Bitcoin private keys would be a very, very bad idea because somebody else could use that data to generate the same private keys and take any money you would have sent to those addresses.

Even still, there are much better ways to generate large numbers of addresses with Hierarchical Deterministic wallets. I highly suggest you look into those.