Keep in mind that your colleagues might NOT want the db to refresh automatically because they might be reading old data to keep track of some numbers/text-- having it change automatically on them tends to be confusing unless the data is known to be temporal in nature (stock prices, ping time, etc).
Why not have your server database have row granularity when presenting results? As in, when someone is viewing the whole db, it just shows up normally and doesn't refresh. Then, when a user clicks a row to edit it, you do a lookup on the db for that row and update it before presenting an update dialog. If you only need the rows updated in order for them to make the proper changes, they only need the specific rows that they are changing to be updating, not the whole data set.
You could have a refresh/auto-refresh button too, of course.
