PostgreSQL or MS SQL?

[johnkawakami]

I'm looking at these two options, and was wondering about which one would be better for hosting a database that will grow to "take over" for a number of legacy systems including Access and xbase? Any other databases to consider?I'm shying away from Mysql. I have a lot of experience with it. I need stored procedures. We can't afford Oracle.The environment here is Windows, but there are a number of older systems that may be DOS. The apps are all pretty old, and part of my task is to port the code into something more modern.The main appeals of PostgreSQL are that its SQL isn't weird, and that there's no per-seat licensing costs. The normal number of seats is around 5, but should grow, and could potentially surge to over 50 at times. Typical per-seat licensing looks kind of expensive to me. Also, if we re-sell portions of the work to our peer organizations, P is appealing because there's no licensing fees.I'm interested in developing something that can be resold (or even given away) for job security reasons.

[chrisatmudd]

I'd go with MSSQL. It's better supported, and if you're looking to hook it up to an Access database, then that's probably the easiest way since you can write custom programs using VBScript or .NET.

[nutwpinut]

My question is what is your OS platform and the applications using the DB. If you are in a Windows environment, I suggest using MS SQL, but if you are in a Linux/Unix environment then I would suggest PostgreSQL. Lastly can you afford MS SQL?From what I can gather from your questions it seems you are in a Windows environment. MS SQL will be easier to manage and use in a Windows environment.