Question:
what is the most reliable database program that can handle full information of 100,000 employees?
paul jordan
2010-04-20 20:13:03 UTC
i work in a large organization having 20,000 employees and continuously growing, we created a database using MS Access to handle personnel information and after 1 yr of encoding info, the data suddenly became random referring to the wrong personnel. some of my colleagues assumed that Access could not handle very large amount of info that's why it became random information.
Eight answers:
RANGARAJAN S
2010-04-20 20:16:11 UTC
You should use either Oracle or SQL Server. If it has large volumes then I would suggest you to use high end databases like Infor or Mapics which are more reliable and secure.
Avon
2010-04-20 21:47:57 UTC
Wow 100,000 employees and you're still using Access! It sounds from the symptoms you describe someone has been messing with your access tables and have removed/changed the linkage.



I worked in a 'Large' company that had just 2000 employees, we abandoned Access RDB tables long ago, we had the main employee database an Oracle HR system, this fed the Billing Matrix and all the other systems that used the unique employee number as primary key.



Because most of our data was held on Oracle systems, we used Business Objects software to produce extremely complex reports very quickly.



The only DB that wasn't linked was the training

system, this was a dogs dinner of a system built using Access db and front end, it was poor when built, but because the system used the employees surname rather than his/her unique employee number, as more data was added it has become worse and worse.



Several of our employees have the same name, some even have the same first, middle and surname, but because this database isn't linked people get mixed up, some who have to attend training courses by law every year have never attended them, others are put on unnecessary courses costing thousands!



Moral of the story is get one reliable master rDB to feed the other systems or risk corrupting your data.
Nigel
2010-04-21 01:32:53 UTC
There are several databases which are up to the task of managing large amounts of information, but the worrying thing from your point is this idea of it 'becoming random'.

Data doesn't just start to forget where it was, or what it was referring to, this could be a symptom of the design of the system used to manage the data not working properly. As part of any project to migrate onto another database, I would also suggest adding some time to investigating the current applications and ensuring they are up to the job.

As for databases - Oracle if you've got the money for it ( you may also need a DBA to manage it as well ). MySQL if you don't want to pay ( although worth getting a support contract in case it collapses at any point ).
anonymous
2010-04-20 20:30:52 UTC
Access can't handle a database larger than 2GB (don't ask me how I know, but it took 2 days to clean up the problem). MySQL can handle it if you want a free database. Oracle can handle it if you want to pay for one and, if you expect to grow a lot larger than you think, RDB7 can handle just about anything you can throw at it if you run it on the right hardware (like a Vax). But we run over 100,000 records on tables in MySQL. It can handle at least 5 gigarows - 5 billion records. (The operating system has to be able to handle a file that large, and you have to have enough disk space.)
GzH
2010-04-21 01:03:38 UTC
MS SQL Server would do the job no problem & you can download the express version free but as the HR side can become complex & you are a growing concern why not look into existing HR software services - this would save you money on new server/DB staff/procedures.



Rather than reinventing the wheel - one example of OpenSource HR management software below - free - they have a hosted service/support service which is very reasonable too



http://www.orangehrm.com/
?
2016-04-14 08:11:56 UTC
This was a great fun piece of reading but Tic Toc Tic Toc, I'm surprised I can still answer this after 22 hours posting....Somebody is asleep somewhere.
AnonymousJohn
2010-04-20 20:15:39 UTC
An SQL server running on a 64-bit box should suit you.
anonymous
2010-04-20 20:16:06 UTC
There is no reason access can't hold that much information, sounds like there was something wrong on either your hardware or something with the input was wrong


This content was originally posted on Y! Answers, a Q&A website that shut down in 2021.
Loading...