Get Rid of 2gb file size limit because Access can be an awesome tool for Ad Hoc data analysis
I can live with the idea that transactional databases >2gb should live on SQL server. But what if I need a tool to investigate data in an 80gb csv file? Yes, I can do this on SQL server, but getting my hands on a server and permissions, etc is a weighty task. Internal data likely already exists in a SQL server (which I can connect to via ODBC), but more and more often I'm dealing with huge flat or csv files from third parties or other public sources.
Access is an awesome tool for ad hoc analysis work, I'd like to work with Big Data with the same ease I work with small data. This is why Access needs a larger file size, not so it can become a larger transactional db as suggested in this post(http://access.uservoice.com/forums/319956-access-desktop/suggestions/10130775-give-us-larger-databases).
Thanks for your suggestion.
At the moment, SQL back-end is how we support larger databases, and there are no plans to change that limitation.
The 2GB limit applies to Jet/ACE, not Access, but the Jet/ACE architecture fundamentally is not scalable and never will be. Fortunately Access works very well with SQL Server as an alternative engine. I think the logical answer to the suggestion here is to make SQL Server better integrated with Access and easier to use without an additional install. See: https://access.uservoice.com/forums/319956-access-desktop/suggestions/10626486-better-integration-with-sql-server