I have just begun drafting a proposal to replace Microsoft Access with PostgreSql as our database system for serving Intranet content to our in-house users here at work. I have been poring over the PostgreSql documentation and Advocacy sites for information to help further my cause. I would also like to poll the users of DevShed for any insight they may have into this project. I would like to hear any suggestions on what I should focus on or include in my proposal to get this done. Here's a little background on what I'm working with / against:
We are developing for a Customer Service Intranet. At any given time, there are approximately 120 people on it at one time. There are not, however, necessarily 120 simulataneous database connections. The platform currently is a WinNT 4 system with a possible future upgrade to XP. We are serving over 10/100 LAN, using perl for server side development and using Access in our production environment.. this last point is the problem and scares me.
This is a Microsoft Shop all the way. If it's not Microsoft, it's tough to convince them to go with it at times no matter the logic.
I did, however, manage to push perl onto the production server instead of ASP.
Our department (and, the whole company as a global entity for that matter) has recently been fixated on cost-cutting like so many others lately.
We already have Sql Server and Crystal Reports. I do NOT know how many licenses we have or would need to purchase if we moved onto Sql Server instead.
I will first be trying to convince my boss who does not have a great deal of expertise of server-side technologies (he's a graphics guy and he seems quite happy to stay that way
). I will then be dealing with administrators who may or may not have any technical expertise on the subject of databases, intranets, and/or server-side programming.
We have a budget - we just choose not to use it, and I don't know what it is...
All that said, I figure I will push the initial implementation costs as a one time thing that beats the overall licensing costs of Sql Server and Oracle (I don't think I can get access to the Oracle server though..). I'll try and get some estimates to compare the overall TCO of PG vs. Sql Server. Of course, I'll also focus on reliability and scalability as well as the overall performance of PG vs. Access (no contest..). I'm going to point to some recent trouble in which we had some databases corrupt in Access and the excessive difficulty that I experienced trying to locate correct and complete documentation for programming Access. I'll also mention the kludges (without saying kludges) that were implemented as a result of limitations in the Access database and the instability that resulted from them. The focus, however, will be on PostgreSql's strong points, no Accesses numerous shortcomings.
Any further input would be greatly appreciated as I'd really like to push a better database into my job so that I don't have to keep fighting with Access....