Nicholson, Karen
knicholson at gpsx.net
Fri Jul 2 10:08:57 CDT 2004
A Stripper? Your programming theory is based on a stripper? This is great news, not the stripper, the performance. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Arthur Fuller Sent: Friday, July 02, 2004 11:04 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Alternative Front Ends I have an ADP that hits a SQL database with approximately 50K customers, most of which have only a few orders, while most of the orders have about 5 details. No problems. Granted, I rely heavily on sprocs to deliver the data, as well as what I call the Sally Rand principle. (Sally was a famous stripper way back when, who coined the phrase, "Show them just enough to maintain their interest." I try to emulate that principle in my designs. I.e., I show one form displaying only a list of company names; select one and then I make visible the subform that shows the details of said customer. Many examples like this; the point is, read in as little data as possible, then wait for a user action.) Strictly for testing purposes, I have created a db called BIG that contains 1M parent rows, 10M child rows and 100M grandchild rows. Relationships are declared and autoForm was used to generate the forms that talk to these tables. I then modified the parent form to include a "finder" on the header that accepts a few letters of the company name, then executes a sproc that performs a LIKE command. The performance is excellent. Arthur -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence (AccessD) Sent: Thursday, July 01, 2004 11:20 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Alternative Front Ends Hi David: There are FEs that are designed to handle more clients like web based ones. There is a trade off as they are slower and do not have as many features. The new vb.net have the capability to be the FE, data web connection and sever side database interface. I have not actually created an applications with the product yet but if it lives up to current billing... An Access FE will work with hundreds of customers. The main issue is what type of BE do you have. It would have to be a SQL DB; SQL2000, Oracle, MySQL etc. on a server or severs of significant power, depending on the application. That volume of data is far beyond an Access MDB. HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of David Emerson Sent: Thursday, July 01, 2004 4:48 PM To: dba-SQLServer at databaseadvisors.com Subject: [dba-SQLServer] Alternative Front Ends Group, A company I am contracting to what to know if there are any "higher" alternatives to Access adp's. They are concerned that Access may not be powerful enough to handle databases with monthly accounts for say 200,000 customers. Any comments? Regards David Emerson Dalyn Software Ltd 25 Cunliffe St, Churton Park Wellington, New Zealand Ph/Fax (04) 478-7456 Mobile 027-280-9348 _______________________________________________ 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 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com