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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

can database acceess handle over than 1 million data a year 7

Status
Not open for further replies.

bantakiah

Programmer
Oct 1, 2006
48
ID
can access handle over than 1 million data a year because i am dificult to get sql server software here thanks
 
[lol] That was kind of funny.

really, I recall seeing studies that access is unstable at 10K. It's a desktop application. Leave it there.

Try looking into SQLExpress.

[sub]____________ signature below ______________
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]
 
I've worked with access databases with many millions of records, and it all worked fine, albeit slowly...

depends on what you want to do with it really...

also, shouldn't this go into the access forums instead of sql server forums?

--------------------
Procrastinate Now!
 
Access has a limitation on the number of concurrent users and as such isn't intended or designed for high-volume, multi-user use.

Microsoft have previously said that they "recommend that Microsoft Access be used solely for development purposes and not for production" so if you are going to be using the database for anything other a local data store for yourself, I'd suggest going with another database.

As has been said, SQL Server comes in a few varieties, one of which is the free Express edition:



____________________________________________________________
Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]

Need help finding an answer? Try the Search Facility or read FAQ222-2244.
 
>> access databases with many millions of records, and it all worked fine

Sorry but that was an extrememly poor business decision. You just do not do this. You cannot reply on desktop application sfor business critical storage and or processing. Be it a middle tier maybe but even at that when and if I see MS Access or any thing such as Excel etc...being used to provide information to the end community it means the people that came up with the specifications all the way down to the development and implementation failed horribly at doing their job correctly. It is an uncontrolled environment and so unstable you're better off attempting to walk a high wire without having two legs

My 2bits and I'll leave it alone now.

[sub]____________ signature below ______________
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]
 
I never said it was a business critical application, just that it worked with millions of records in it...

also, the general concensus is that access can handle about 20-30 concurrent users, however in my opinion, concurrency does depend heavily on how you design your system, e.g. you will have less problems if you don't use bound forms...

--------------------
Procrastinate Now!
 
Definition of a business critical solution you and your IT department provides to the end users community?

Anything you give them!

That is what will make or break your success in your career

IMHO

[sub]____________ signature below ______________
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]
 
if only things are that straight forwards...

--------------------
Procrastinate Now!
 
I know of a corporate-wide application where I work that is built entirely from Access. It's a slow snail, and it takes ~ 20 minutes to "submit" files to a source system.

To make a long story short, I'm with onpnt, don't use Access to try to handle large databases.

[monkey][snake] <.
 
I've made a small fortune taking business critical solutions developed in Access (and Excel too for that matter) that ended up totally hosed/out of control/impossible to maintain-support and turning them into REAL business critical solutions using SQL Server and (choose a UI programming language - Access included!).

Just because you CAN do a thing doesn't mean you SHOULD!

< M!ke >
Acupuncture Development: a jab well done.
 
Access applications are for rogue users who spread their little virus around the department. When the file size exceeds 2GB they come crying to us. When the coder's logic spits out incomprehensible garbage, they ask us to fix it.

"Sorry, that's not a supported application."

I'm with Mike. We upsize or replace Access apps at every opportunity.
 
I write a lot of applications in access, and use SQL server as the back end for nearly all of them. Our SQL server is not really that heavily used though, if it was I would consider leaving some access - only. What I really hate about access is the jet engine. I have written some queries that won't run in access (usually involving different calculations using data from multiple tables), but if I put the exact same tables in SQL Server, link to them, and run the query that way they work fine. This frustrates me to no end!

If you are adding 1 million rows per year, and your tables are even a little wide, I'd think you would outgrow access rather quickly. I am looking at an access db sent by a client right now for some data overlays and analysis that is 1.6 gb (performance is ATROCIOUS!). By my rough estimation, this has 5-6 million rows in it (3.2 million in the main table). So, as a short term solution, access will probably work for you. If you want something more dependable over the long term, go with SQL Server.

Hope this helps,

Alex

Ignorance of certain subjects is a great part of wisdom
 
Microsoft actualy used Access as the Meta-data store for Analysis services in SQL2K. You could upgrade it to SQL. I can't remember how many times the access DB would get corrupt due to the size of our AS definitions.

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck
 
>>You could upgrade it to SQL

that is the first thing I did ;-)

IMNSHO Access and that other Shelfware product FoxPro are a big pain in the neck to work with

Exclusively locked files, corrupt files, no way to roll back or do a point in time restore etc etc etc

Denis The SQL Menace
--------------------
SQL Server Code,Tips and Tricks, Performance Tuning
SQLBlog.com
Google Interview Questions
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top