[eluser]WanWizard[/eluser]
There are some third party libraries around that are drop-in replacements for the session library, notably native_sessions (that uses a file for each session). See the wiki.
I don't see what the problem is with session update. As long as the session is valid, the same record is updated. Only after the session is expired a new session record is created. You have to think about a proper session expiration time for your application.
If you set sess_expiration to 0, the session library with set it to two years. CI 1.7.2. doesn't support 'expire on browser close', CI 2.0 does.
If you set sess_time_to_update to 0, it will rotate the session id on every request, which is a bit over the top...
Note that if you now have an issue with to many session records, switching session libraries won't help, they will create the same amount of sessions, just on a different storage medium.