Does your Access database corrupt often? queries taking longer to complete? reports taking longer to print?
Would you like your users to have access to your data without having to install Microsoft Access?
If you answered 'yes' to any of these questions, you are a prime candidate to upsize your Access database to SQL Server.
In a typical Access applicaton, the database is split into two components: the data store and the user interface. The data store is normally located on a shared folder on the network, while the user interface is run from the client workstation.
When a user opens a table or form, runs a query, or prints a report, the interface component pulls all of the records in the data source(s) across the network to the workstation. Access then determines which records it needs. As your data tables grow, the corresponding network traffic increases dramatically, thereby not only slowing down your Access applications, but also slowing the network in general.
When an application is properly designed using SQL Server, the filtering of records is done on the server, and only the needed records across the network. An application will thus work faster because (a) it spends less time wating for the records to be returned to the workstation and (b) the workstation does not perform any record filtering.
The following are some of the typical efficiencies acheived after converting an Access database to SQL Server.
- Ability to handle more concurrent users
- Larger physical data files
- Decrease in network traffic (only needed records are sent across the network)
- Ability to 'rollback' a series of transactions if the entire series is not properly handled
- Near elimination of corrupt data files
- Faster recovery from data disasters due to SQL Server's event logs
- Choice of either an Access, Visual Basic, or web browser front-end
Subscribe