MS Access vs SQL

1,106 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,106
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
51
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

MS Access vs SQL

  1. 1. MS Access vs SQL
  2. 2. Options <ul><li>Microsoft Access (Jet Engine) </li></ul><ul><li>Microsoft Access (MSDE) </li></ul><ul><li>MS SQL </li></ul><ul><li>MySQL </li></ul><ul><li>Other SQL applications </li></ul>
  3. 3. Access – File Server Architecture <ul><li>Server is a storage device only </li></ul><ul><li>Access database tables stored on server </li></ul><ul><ul><li>Queries, forms and reports can be on the client or server </li></ul></ul><ul><ul><ul><li>Better performance if stored on the client </li></ul></ul></ul><ul><li>Client request leads to all related tables to be transmitted to client </li></ul><ul><ul><li>Performance typically acceptable in LAN </li></ul></ul><ul><ul><li>Performance suffers on WAN (slow) links </li></ul></ul><ul><ul><ul><li>Larger tables can take many minutes (or longer) </li></ul></ul></ul><ul><li>All processing then done on the client </li></ul>Client / Workstation Server
  4. 4. SQL – Client/Server Architecture <ul><li>Server is a processing partner and storage device </li></ul><ul><li>SQL database tables stored on server </li></ul><ul><li>Client request leads to processing on server(s) </li></ul><ul><li>Result is sent to the client for formatting & display </li></ul><ul><ul><li>Performance much better particularly on WAN (slow) links </li></ul></ul><ul><ul><ul><li>Much smaller amount of data transmitted </li></ul></ul></ul><ul><li>Both sides can perform relevant data processing </li></ul>Client / Workstation Server
  5. 5. Client Server Database Systems
  6. 6. MS Access vs. SQL Server <ul><li>MS Access </li></ul><ul><ul><li>Great for small projects with just a few users </li></ul></ul><ul><ul><li>Great tool to develop custom business applications, since it's free to distribute and relatively easy to use </li></ul></ul><ul><ul><li>Problems arise when you need to scale the application for </li></ul></ul><ul><ul><ul><li>More features </li></ul></ul></ul><ul><ul><ul><li>More data </li></ul></ul></ul><ul><ul><ul><li>More users </li></ul></ul></ul><ul><li>Microsoft's SQL Server 2005 </li></ul><ul><ul><li>Designed to handle </li></ul></ul><ul><ul><ul><li>Data administration </li></ul></ul></ul><ul><ul><ul><li>Rigorous workload balancing of enterprise applications </li></ul></ul></ul><ul><ul><li>Can connect directly to existing MS Access application </li></ul></ul>
  7. 7. MS Access Guidelines   &quot;ok&quot; &quot;Caution&quot; &quot;Stop&quot; LAN Users <5 5-10 > 10 Internet Users 0 1 > 1 User Permissions Read-only Read / Write Read / Write Size of DB < 100 MB 100-300MB >300MBs Data Structures Simple Moderate Complex DB Schema Design Well Designed Poor Design Ad Hoc
  8. 8. MS Access (Jet) Scalability <ul><li>Access Jet Engine – 5-10 simultaneous users in the LAN </li></ul><ul><li>If database is on the Internet requires “real” SQL Server License </li></ul><ul><ul><li>Strictly a licensing (revenue) issue </li></ul></ul><ul><ul><li>Exceptions: </li></ul></ul><ul><ul><ul><li>MS Access front end – limits the number of End Users you can support </li></ul></ul></ul><ul><ul><ul><li>.ASP Active Server Pages – read-only access to your data </li></ul></ul></ul>
  9. 9. Users and Internet Support
  10. 10. Access Jet vs. MSDE <ul><li>Access Jet Engine database back-end </li></ul><ul><ul><li>Default Access database engine </li></ul></ul><ul><ul><li>Simple database schema </li></ul></ul><ul><ul><li>Don't expect database to grow larger than 1.5 GBs </li></ul></ul><ul><li>MSDE </li></ul><ul><ul><li>Microsoft SQL Server Desktop Engine </li></ul></ul><ul><ul><li>Works with Access application front-end (Client) </li></ul></ul><ul><ul><li>Identical to MS SQL Server </li></ul></ul><ul><ul><ul><li>MS SQL Server – license is required </li></ul></ul></ul><ul><ul><ul><li>MSDE – free </li></ul></ul></ul><ul><ul><ul><li>Certain performance limitations and licensing restrictions </li></ul></ul></ul><ul><ul><li>Not be supported on the Vista OS </li></ul></ul><ul><ul><ul><li>Upgrade to SQL Server 2005 Express </li></ul></ul></ul><ul><ul><ul><ul><li>Maximum database size of 4 GB </li></ul></ul></ul></ul>
  11. 11. MSDE Scalability <ul><li>Extends LAN capabilities </li></ul><ul><ul><li>Not licensed for the Internet </li></ul></ul>
  12. 12. MS SQL Server Scalability <ul><li>Mission Critical Enterprise Applications </li></ul><ul><li>Supporting dynamic Internet applications </li></ul><ul><ul><li>Static vs. Dynamic Content (Read vs. Read-Write access) </li></ul></ul><ul><li>Frequent user access </li></ul><ul><li>Large number of end users (enterprise-wide deployment) </li></ul><ul><li>Size of the database greater than 100GB </li></ul><ul><li>Auditability, Industry Compliance (e.g. SarbOx, HIPPA) </li></ul>
  13. 13. Front-end Comparisons
  14. 14. Split a Microsoft Access Database <ul><li>Into two files </li></ul><ul><ul><li>One with the tables </li></ul></ul><ul><ul><li>One with the queries, forms, reports, macros and modules </li></ul></ul><ul><li>Microsoft Jet database engine manages the data </li></ul><ul><li>Users can access the data with customized forms, reports, pages, and other objects while maintaining a single source of data on the network </li></ul><ul><ul><li>Users have only the resources they need </li></ul></ul><ul><li>Course Text </li></ul><ul><ul><li>Microsoft Office Access 2003: Comprehensive Concepts and Techniques </li></ul></ul><ul><ul><ul><li>Project 9 – Page AC 569 </li></ul></ul></ul>
  15. 15. Split a Access Database (1 of 2) <ul><li>Use the Tools | Database Utilities | Database Splitter. </li></ul><ul><ul><li>Follow the instructions in the Database Splitter Wizard </li></ul></ul>
  16. 16. Split a Access Database (2 of 2) <ul><li>Choose name for backend (tables) file </li></ul><ul><ul><li>End up with Access DB with only the local tables </li></ul></ul><ul><li>Move backend to Server </li></ul><ul><ul><li>Could have been done within the Wizard </li></ul></ul>
  17. 17. Linked Table Manager (1 of 2) <ul><li>Use the Tools | Database Utilities | Linked Table Manager </li></ul>
  18. 18. Linked Table Manager (2 of 2) <ul><li>Use the Select New Location box to find the Server (tables) </li></ul>
  19. 19. Fin…

×