March 13th, 2010, 9:48 am
QuoteOriginally posted by: DominicConnorI also lean towards SQL Server, it will import Access DB's directly and is about the easiest to use of the major DBs.Yes, it's "enterprise" but has a nice GUI, wizards, good online help and if you go for the entry level stuff it's cheap or free.KDB is overkill for what you want, and both costs more and is considerably harder to use.Mysql will handle the work with ease, but I'm assuming that you aren't a DB professional and don't want to be, so it's a bit more work than it needs to be.Oracle is the least optimal choice because it's not as friendly, and costs more, and if you're really unlucky some shithead from Oracle will find out you're using it and try to make life hard for you, your boss, and the girl you met in the bar last year. However you do this be aware that Access has different ideas about data types than any real database. I've got an MS SQL Server manual which lists "differences between Access SQL and Microsoft SQL", that's how screwy it is. This can hit you with timestamps especially.I'm currently working on a project with MS SQL, importing huge datasets from Excel (which is badly formatted). It is almost impossible to get it in. I believe in one instance I had to export as CSV, import into Access and then into MS SQL. Although, I'm inclined to believe this is the data's fault, not the products.