access or sql
Posted on 2015-01-28
I am hoping someone can help me out with some rough guidance on a database.
I provide a few days of support for a small business that a friend of mine owns, i do it for free just to help him out.
The business is an electrical company who have a microsoft access database which tracks their engineers diarys, jobs, invoices, parts etc
I know very very little about databases - the most i have done is link tables in the past at a previous job - in my day job i deal with cisco infrastructure equipment so i'm really in the dark here! I have always approached databases that my little knowledge is dangerous rather than helpful so it is best left to an expert.
The database system is continually crashing, multiple times a day and requires 'compacting'.
The person they are employing to maintain and customise their database continually comes up with excuses as to why the database is crashing and i am not so sure they are all true so i am hoping to get a second opinion on here.
The database has around 7 to 10 users at any one time.
It has been running now for a number of years and over time, has got worse and worse, crashing more frequently.
The business is growing as is the amount of data going into it - from external advice and reading around on the web, SqL seems to be the way forward but the DBA seems to be reluctant to do this or even entertain it.
First the DBA blames the server, so we move the DB to a new server - problem still persists
The DBA then blame office 2007 and makes the company upgrade to 2013 - problem still persists
Then the DBA blames the network - that there must be an issue - testing proves there is no issue
I wanted to ask the question
- Is there a limit to how big a database should be? Or is it too big and that is why it keeps crashing? (if someone can tell me how, i could easily find out the amount of data / number of tables or records etc inside there, or just the file size)
- is there a maximum number of users that should be on at one time?
- would moving to SQL benefit? I am under the impression for a server based, multi user, large (if it is large) database would run much better in sql?
- at the previous company the DBA made a front end and a back end... each user had 'their own' front end which linked to the same backend data and this did make things a bit better, does this normally help?
any help would be appreciated, and i understand the info above is patchy at least, if someone were to guide me i could get any required information...
thanks in advance!