index | search | no replies | posting guidelines | help | login | register |
Index » Products » ASP Report Wizard v2 |
| |||||||
Aug 31 2004, 11:50 AM |
| ||||||
scotthibbs![]() ![]() from: Philadelphia, PA | I have a question regarding performance. Based on the way your component accesses data internally, would it be more advantageous to: a) limit the number of rows in the views we expose to the user with the TOP SQL statement...i.e. Select TOP 5000....etc. b) use the new property, MAXRECORDS, of your component. I have been concerned about the consequences of a join that a user might do between our views if we add the TOP statement. I would prefer to use your property if it is actually limiting the sql server resource usage and not limiting just what is displayed, which would benefit the web server more than the SQL server. Any info on how you handle the MAXRECORDS property internally would be appreciated. | ||||||
Aug 31 2004, 7:09 PM |
| ||||||
whichman![]() ![]() ![]() from: Laurel, MD | Yes, we set the recordset property directly on the database server. I will also add the percentage option for SQL Server which will be available in the next release ------------------------- Master of the Game | ||||||
Sep 1 2004, 7:56 AM |
| ||||||
scotthibbs![]() ![]() from: Philadelphia, PA | So you would advise using your property.....correct? How will the percentage option work? What will be it's function? Thanks | ||||||
Sep 1 2004, 10:06 AM |
| ||||||
whichman![]() ![]() ![]() from: Laurel, MD | Yes, because we set it directly on the database server The percentage just returns a percentage of the amout of records in the table. It will work using the MaxRecords property. For example: objWiz.MaxRecords = 3000 or objWiz.MaxRecords = "30%" (SQL Server & Access Only) ------------------------- Master of the Game | ||||||
Pages: (1) [1] |