I used to work for a student information system company. These systems are all ancient, designed around a time when a dozen people would connect to the server using their green screen terminals or, in a spate of massive innovation, Oracle Forms.
As a result, all of the web access must be done through a single db server. Any app (including the portal) tends to directly access the db, causing all sorts of stored procedures to run. Nothing is cached. The server is only busy twice a year, fall and spring semester registration, so there is a limited desire to spend more than they absolutely have to on it.
Over all, IT in higher education in an interesting mix. There is a decent percentage of really good people there, who love the environment and are willing to give up the salary as a result. Unfortunately, there are also at least as many people who are earning what they are worth. The less prestigious the school, the higher the percentage of the latter.
As a result, all of the web access must be done through a single db server. Any app (including the portal) tends to directly access the db, causing all sorts of stored procedures to run. Nothing is cached. The server is only busy twice a year, fall and spring semester registration, so there is a limited desire to spend more than they absolutely have to on it.
Over all, IT in higher education in an interesting mix. There is a decent percentage of really good people there, who love the environment and are willing to give up the salary as a result. Unfortunately, there are also at least as many people who are earning what they are worth. The less prestigious the school, the higher the percentage of the latter.