G
Guest
We have an Access database that over the years is getting pretty big. It
gets its data from two sources: a coldfusion web app, and a third party
application that handles faxed forms. Analysts will also connect directly to
the tables using SAS to extract data. There is no Access front end for the
users and the database is not split.
The database owner is against migrating to SQL at this time. Since I've
been affected by a couple of other Access databases that imploded, I was
wondering what risk he runs by letting an Access db get bigger and bigger?
Are there any guidelines for when you would want to migrate to SQL based on
size? Also, since there is no Access front end to speak of, what are the
risks of data corruption given the above connections?
Thanks
gets its data from two sources: a coldfusion web app, and a third party
application that handles faxed forms. Analysts will also connect directly to
the tables using SAS to extract data. There is no Access front end for the
users and the database is not split.
The database owner is against migrating to SQL at this time. Since I've
been affected by a couple of other Access databases that imploded, I was
wondering what risk he runs by letting an Access db get bigger and bigger?
Are there any guidelines for when you would want to migrate to SQL based on
size? Also, since there is no Access front end to speak of, what are the
risks of data corruption given the above connections?
Thanks