Metabase.xml

I have a script that I wrote on an ASP page.. I recently applied it to a different DB and it gives an error


Now this script worked on a different db that was much smaller. All my searches said I need to edit the metabase.xml and increase the asp buffer size.

ummm dumb question here .. where do I find the metabase.xml file... a search does not show it and it is not in my inetpub directory.

Here is the code in question... I cut some junk out that was unnecessary (table row, table data .. that type of stuff).

The file is stored in %SYSTEMROOT%\system32\inetsrv as META BASE.XML. Note the space in the middle. Cute, huh?

Reference:
http://www.pcquest.com/content/serv...e/103060301.asp

Joe

I think your problem is a coding problem not an IIS problem. I'd be reluctant to try to modify any IIS settings to solve this.

I agree with Doug G, but if you want to modify IIS metabase.xml you must tell us what version of Windows do you use...

Windows 2000, WindowsXP, Windows 2003 ?

If you use Windows 2003 then you can locate metabase.xml in...
%SYSTEMROOT%\system32\inetsrv
and edit it with notepad or vim (careful with other editors for whitespace...)

If you use Windows 2000, WindowsXP then you must search in Microsoft's site for the tool MetaEdit 2.2 !
Why ??? Because, there is no metabase.xml file and it is very difficult to edit the metabase.bin file.

Normally I would be the first to suspect a code error. But in this particular case I dont see how it could be.

1. the code works great on a smaller db (several hundered rows).
2. I am not doing anything too dificult. A simple "select where " statement, then assigning variables, then printing the variables in a table, then rs.movenext, then Loop.

Do you guys see anything obovious in the code I posted?

I bumped up the buffer limit and it worked, but needless to say I am unimpressed with the performance. The new db has 5k rows where the old one had somewhere 6 to 7 hundred.

Do you guys think I would get better performance by using a view in the SQL server? OR a SQL Query that is in the Query section IN the SQL database?

Review your sql and also review your database indexing

I might be wrong but I think you should be able to retrieve the records 500 at a time, 1000 at a time etc using paging...???

If your code works ok with a smaller sample, but dies when you retrieve more rows, then you definately need to handle that in your code - don't start mucking around with IIS settings otherwise you risk overloading your server - imagine several people running the same query at once...