Microsoft Site Server Information

Tuning/Performance Information

use system DSN instead of file DSN - Microsoft says it's 3 times faster
get rid of MSCSQueryMap objects in global.asa to free up memory - just use straight asp code on individual pages, but it's harder for maintenance
set enable_sessionstate=false at start of each asp page so as not to incur extra overhead, even if not using sessions
if include i_shop.asp make sure as to close connections on each page that includes it because it opens one up - also it's expensive overhead-wise to open a connection so don't include it if it's not needed
for non MTS objects instead of Server.CreateObject("ADODB.Recordset") use <OBJECT ...> tags (not SCOPE=APPLICATION) like in global.asa - that way won't bother instantiating connection until first property is set - good if have error to send back to user even before any database work
take out any component/stage not used in pipeline - like when go through every item again to get price when do final purchase stage (if you know prices don't change that often)
go to http://www.microsoft.com/siteserver/commerce/deployadmin/ - look at Edit Dictionary.asp and Volcano Coffee Sample Site and Performance Kit
on ASP pages you can "dump" HTML to the user by simply adding it outside the ASP delimiter tags; however, ASP takes a performance hit when you do this. The ASP.DLL engine has to parse out the HTML to send it to the user's browser. This takes more time than building a series of Response.Write statements. (didn't get this tip from the class)