I have a page that loads a recordset of about 200 employee records and it takes about 20 seconds to load. Isn't there a way to load part of the records display them and load more so the browser doesn't have to stare at a blank screen?
I'm pretty sure there's a problem using Flush for what you're asking. I use it to put up a "Processing..." message, then replace it with a "Complete" or "Error" message when carrying out lenghty tasks.
I'm having trouble with the 20 seconds part...I have 4000+ size recordsets that can be processed, streamed to client, and displayed in less. You may want to check some of the efficiency posts in the FAQs section, as well as the post here in the last day or so about speeding up pages. It's possible you could speed the system up by several more factors.
With table-layout: fixed browser analyzes only first row, takes column widths and apply them to the rest of table. This speeds up rendering, especially on larger tables. But if column widths for first row aren't specified... you got the picture. Just specify column widths once (TH tags or COLGROUP/COL section is logical place to do that).
Btw. this only gives illusion of faster loading (aka: shorter beginning of response). 20 seconds for 200 employees is too slow IMO... problem is probably somewhere in queries/database code.
This is my first time working with sql server, and I have been reading about stored procedures. can a stored procedure be used to populate a recordset. if yes would this speed up the client's navigation speed?
Yes stored procedures can be used to populate a recordset - but don't use them ASAP. Better show us ASP code that SELECTs employee records and renders data into HTML table.
I want to put 100 employees per page but I don't want the client to have to wait. When I used the fixed width property it seemed to display records right away but 2 of my rows on the main encompassing table were getting messed up. This is the code for the 2 rows:
If you guys have additional suggestions on how to speed things up or maybe I can just use the fixed width property if I can get thos rows to display correctly.
Got a little bit confused here... the part that displays data and first two rows are the same table? If true, split data part into separated table and apply fixed layout on it.
Unless there are bazillion employees in database, this query should fly. How quickly page stops if you write Response.End after rsEmployees.open() ?
Btw. there is too much (Dreamweaver? UltraDev?) HTML cr@p here... simple CSS can cut generated HTML to 1/3 in size.
And... no need to write = rsEmployees.Fields.Item("blah").value... = rsEmployees("blah") is enough.
It was more like 14 seconds. I'm running time warner cable through a firewall. I'm building a huge Intranet and trying to figure out the most efficient way to do it. So far I understand that SQL server is a lot more powerfull than access which is what I've been using until now. Is SQL better only in instances where you have a lot of users browsing at the same time or does it perform the same as access when there are only 1 or 2 users?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.