Database & SQL
It looks like you're new here. If you want to get involved, click one of these buttons!
C and C++
Delphi and Kylix
DirectX Game dev
Newbie Game Programmers
Database & SQL
Sound & Music
FreeLance Software City
Join the Team
Comments on this site
New programming languages
Off topic board
Mobile & Wireless
Operating Systems & Platforms
Embedded / RTOS
Windows CE & Pocket PC
Quality & Testing
Active Server Pages
HTML & WEB-Design
WEB-Services / SOAP
We have migrated to a new platform! Please note that you will need to reset your password to log in (your credentials are still in-tact though). Please contact firstname.lastname@example.org if you have questions.
Tweets by @pheaven
difference between Access and Oracle
Database & SQL
can you guys tell me the pros and con's of access and oracle
which one is better??, why ?? thank you
: can you guys tell me the pros and con's of access and oracle
: which one is better??, why ?? thank you
To my understanding, the differences are as follows:
Access is a small database system, which will allow you to create a small-medium sized database with minimum security features. Oracle can be integrated with NT security, which gives tight control over who can and cant get to your data.
Access is a lot slower over networks as all the processing is performed on the client machine, whereas with a large DBMS like Oracle (Or SQL Server), you send only a query (such as "SELECT * FROM Customers WHERE CustID=23;"), and only the required results are returned. If you ran this across a network with Access, all the records would be sent across the network, leaving the client machine to select the required record.
Access gets really slow if you try to connect more than 10 users (depending on the size of the DB and how it is being utilized), where are Oracle can accept hundreds/thousands of simultaneous connections (Depending upon the server it is sitting on).
The final major difference is that of triggers and stored procedures. Access can NOT store procedures which can be executed remotely. You can write functions and with a bit of "jiggery-pokery" get the server side to execute them vy setting flags or something in your database and getting the server to check at pre-defined intervals if the flag is set. With Oracle/(Other Large DBMS's) you can call the stored procedures and they will be executed on command on the server side. Triggers are like events on an Access form, such as "After-Update". When you update a record into Oracle, you can set triggers to automatically run procedures to check for pre-defined rules or whatever.
Oh yeah, and Oracle will cost you an arm an a leg in money and set-up/maintenance time.
For small databases, where only 1 or 2 users need to access the data, I recomend Access, for Enterprise-size solutions, you really need A Server DBMS such as Oracle/SQL Server.
Hope this helps.
: For small databases, where only 1 or 2 users need to access the data, I recomend Access, for Enterprise-size solutions, you really need A Server DBMS such as Oracle/SQL Server.
Of course, there is a middle ground in the form of MSDE (which is freely downloadable from Microsoft's site). This provides an SQL Server-compatible database engine that is suitable for over a hundred users. It can't be clustered, etc., but it's still a client-server database, and being SQL Server you can use Access 2000 to administer it easily.
: : For small databases, where only 1 or 2 users need to access the data, I recomend Access, for Enterprise-size solutions, you really need A Server DBMS such as Oracle/SQL Server.
: Of course, there is a middle ground in the form of MSDE (which is freely downloadable from Microsoft's site). This provides an SQL Server-compatible database engine that is suitable for over a hundred users. It can't be clustered, etc., but it's still a client-server database, and being SQL Server you can use Access 2000 to administer it easily.
There is another major factor to consider. Oracle/SQL Server/DB2/other enterprise db engines are MUCH MUCH more stable. When properly set up, these machines can even lose power to the server without losing more than the most recent database actions. Backup/recovery/stability is the single most critical issue if your database is mission critical or vital to your business. Oracle can be configured so that drive failures or power loss loses no more than 3 seconds of data, tops. Access has no such ability to maintain redo or archive logs of updates.
About & Contact
User uploaded content
Programmers Heaven C Sharp ebook
Operated by CommunityHeaven LLC
- All rights reserved.