Dan Waters
df.waters at comcast.net
Fri Sep 10 13:43:41 CDT 2010
Hi John, The trick is binding a form to a table. What's the plan to do that? For Access user limits, it's my understanding that the throttle (governor) is the .ldb file on the BE .mdb. This .ldb file is being continuously 'managed' by all the users currently logged on - as you increase the number of users, the .ldb file management slows down from the perspective of a single user. As the server's CPU speed increases and as its memory increases, the slowdown will begin to happen with a higher number of users. Of course, SQL Server doesn't have an .ldb file, and it will manage concurrency internally and more quickly. I have an Access Que 2003 book which states that developers expect to see a slowdown at about the 10 to 30 user point. But that was written eight years ago when CPU's were slower and memory was less available. HTH! Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Friday, September 10, 2010 1:09 PM To: Access Developers discussion and problem solving; Sqlserver-Dba; VBA Subject: [AccessD] SQL Server Express - true skinny Does anyone know the true skinny on the limitations placed on SQL Server express in order to "throttle" it.? I found a blog that claims that outside of CPU / Memory / DB size limitations, there is not other "governor". So it appears that the limitations are: 10 gig db file size. This does not discuss additional database files. 1 CPU. However it appears that it can use 4 cores if available 1 gig of memory. This appears to be the killer. But there appears to be no "user" limitations etc. So the question is, would SQL Server express be capable of replacing Jet for a complex bound application for 30 users? -- John W. Colby www.ColbyConsulting.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com