Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Guidlines for Database Sizing
- Thread starter SylviaE
- Start date
Difficult question to answer without knowing the nature of your data model and other requirements. "My" general rule is to consider the following:
1. Database size:
If over 200,000 records in a primary table(s), the use a full-scale DBMS, like SQL-Server or Oracle.
2. Archives/Backups:
For mission ciritical enterprise systems I would recommend a full-scale DBMS.
3. Multi-User Access:
Again, For mission ciritical enterprise systems I would recommend a full-scale DBMS. Especially, if the number of concurrent users exceeds 20.
One thing to consider is that you can start with Access then easily scale it to SQL-Server if necessary. That is provided you design to data model within the architecture compatible with SQL Server. I've done this in the past with little trouble.
Again, just my guidelines.... htwh,
Steve Medvid
"IT Consultant & Web Master"
1. Database size:
If over 200,000 records in a primary table(s), the use a full-scale DBMS, like SQL-Server or Oracle.
2. Archives/Backups:
For mission ciritical enterprise systems I would recommend a full-scale DBMS.
3. Multi-User Access:
Again, For mission ciritical enterprise systems I would recommend a full-scale DBMS. Especially, if the number of concurrent users exceeds 20.
One thing to consider is that you can start with Access then easily scale it to SQL-Server if necessary. That is provided you design to data model within the architecture compatible with SQL Server. I've done this in the past with little trouble.
Again, just my guidelines.... htwh,
Steve Medvid
"IT Consultant & Web Master"
- Thread starter
- #3
Microsoft will tell you to start it in Access and then migrate to SQL server. That way they get to sell you both products...
Remember, you're unique - just like everyone else
You're invited to visit another free Access forum:
or my site,
Remember, you're unique - just like everyone else
You're invited to visit another free Access forum:
or my site,
- Thread starter
- #5
Remember, if you design your Access database correctly with the intention that it will eventually be scaled to Oracle you will have no trouble. A database is a database...
One piece of advice, make sure all field names are Upper case and no spaces. This one caught me before scaling from Access to Oracle.
Steve Medvid
"IT Consultant & Web Master"
One piece of advice, make sure all field names are Upper case and no spaces. This one caught me before scaling from Access to Oracle.
Steve Medvid
"IT Consultant & Web Master"
- Status
Similar threads
- Locked
- Question
- Locked
- Question
