Storing salts

You are working with a company that recently had their database for their custom intranet system cracked by hackers. The company has determined that its 10-year-old system had several flaws that allowed the breach to occur. One of the primary vulnerabilities the company discovered was that the application stores users’ passwords in clear text. The company is refactoring its application to eliminate the vulnerability. One of its requests is for the application to use salted and hashed passwords. Although company decision makers know salted and hashed passwords are necessary, they cannot agree where to keep the salt. One party feels that keep-ing the salts in a separate column of the Users table is sufficient, whereas another party feels that it should be kept in a second, differently credentialed database that is used only for saving and retrieving salts.

What are the advantages of storing the salts in a separate database?
What are the advantages of storing the salts in the same database?
Which would you recommend?