Arthur Fuller
fuller.artful at gmail.com
Thu Mar 20 22:38:52 CDT 2008
I think that I was one of the earliest adopters of the ADP approach, which lets you talk directly to SQL Server from Access. In that scenario, all that lives in Access are the forms and reports. So you get the best of both worlds -- RAD in Access and performance and scalability in SQL Server. In the biggest such app I did, I had over 70 simultaneous users hitting a SQL db that was about 3.5 gigs. In a test scenario, I had an Access ADP hitting a 20 gig db with no issues. A. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Paul Nielsen Sent: Thursday, March 20, 2008 5:37 PM To: 'Discussion concerning MS SQL Server' Subject: [dba-SQLServer] Access limitations As a SQL Server only guy, I'm unfamiliar with how far you can scale Access today and still expect it to behave well and be stable. But this group might know. How large can an Access database become before you begin to feel nervous? And how many concurrent users? Assume you have great hardware and a networking infrastructure. -Paul _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com