Suitable RDBMS.

S

Shotodru

Dear Friends,
Without entering into any controversy on which is the best R/DBMS, I would
like to seek your advice on which, in my situation, would be the suitable or
ideal R/DBMS to use.

My situation is that, I am in the process of developing a database
application which would store about a million records each financial year.
At the end of each financial year, these records would be archived.

On a thumb rule estimate, there would be about 25 unique fields in each
record - 10 field would be unique while the rest are all character-based.

Security: This is not a concern.

Initial No. of Users: Immediately on deploying the application, 2 users
would concurrently keep on accessing the database almost 24x7.

Projected No. of Users: There may be a concurrent number of maximum of 5
users.

Data Backup: This feature is very important and is an absolute must.


Can anyone please advise.

Best Regards,
Satadru
 
A

Arvin Meyer [MVP]

That may be stretching the limit of a desktop database (either Access or the
MSDE). Both could handle a million records provided the data could be
contained within a 2K row, but you will be pushing the limits. The 24/7
access rules out Access/Jet if you can't close it for a few minutes of
maintenence and backup.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
S

Shotodru

Thanks Arvin. I do believe that my requirements may push Access to its
borders. Sure I can spare about an hour or so on maintenance activities. But
would it allow for 5 simultaneous users?

Best regards,
Satadru
 
C

Craig Alexander Morrison

I wouldn't be surprised if people here said Access with a little SQL Server
2000 Desktop on the side. :)

I wonder what the answer would be on a FoxPro, Oracle, DB2, SQL Server,
Paradox, FileMaker.....newsgroup. (vbg)

Access 2003 and Jet 4.0 (aka Access 2003) would satisfy these requirements
easily, although this depends on what you mean by backup. Using Access with
a DB2 or SQL Server backend may be more appropriate. Jet backups are simply
file copies (when the database is not in use) of the MDB containing the
data. DB2 and SQL Server can backup while the database is still available to
users and maintains transaction logs allowing recovery functions way above
those available on a Jet database. As you say almost 24/7 DB2 or SQL Server
looks like the way to go unless there is a period of inactivity when the
closed database can be backed up.

--
Slainte

Craig Alexander Morrison
Crawbridge Data (Scotland) Limited

BTW SQL Server 2005 Express available shortly and for free is worth every
penny. (vbg)
 
Top