Re: Using SQl to store aspx pages and memory problems

DLM,

Thanks for your response.

I don't believe that SQL is my problem - the time it takes to do the remote
calls to the external program has not presented any real limitations or
caused any significant time-delays. The problem that I have is trying to
deal with the quanitity of files that I have and the combiling of those pages
once they have been returned. Any time issues that I have had are the result
of parsing and compilling the page.

I understand your point - that asp.net was designed to have the pages
pre-compiled before requests where made for the pages - I guess this is one
of the fundamental differances between asp and asp.net. From experiance the
design that has been implemented had no significant disadvantages when
working with asp - in fact I believe that it had some very significant
advantages - mainly due to the unlimited number of files it could manage.

Question - is it practicale to have 10,000 pages in a single asp.net
application. I wouldn't have thought so?

I have no alternative but to deal with this many files as it is a legal
requirment of the industry I work in is to be able to provide the original
copies of invoices to clients - I can't go back to the original data and
attempt to re-produce the same invoice just in case the data has changed.

So - considering this is what I am stuck with - my problem mainly relates to
the memory increases - the slowness of the request could be dealt with by the
more grunt - but the ever increasing memory is more difficult. I believe
that this is the result of the creation of a new class each time a new page
is displayed - although this page gets un-loaded once the info is returned -
are the increases in memory the result of the new class definition in the
asp.net application?

If this is the case - is it possible to remove this class definition once it
has been created? I have tried to delete the file - but this does not appear
to fix the problem.

Does any of this make sense.


--
matthew


"DLM" wrote:

> Go to this link:
> http://www.theserverside.net/books/inreview/ImprovingPerf/pag.tss
>
> We all know that there is an initial performance 'hit' the first time a ASP
> .NET Page is requested, and this is true with the page sitting in it's
> virtual directory on IIS. What you seem to be doing is increasing the round
> trip time for any given request/response for a page to include the time it
> takes to get the page from SQL Server. And this added time is database access
> time which is probably longer than any HTTP request.
>
> I have never seen this kind of architecture before. The whole idea is to
> serve pages from a highly scalable architecture such as IIS from the very
> start, and not make the ASP .NET worker process wait for the files before it
> can dynamically compile pages. In a sense you are using SQL Server as a web
> server to your web server, which is highly unusual. You need to find a way to
> place all your pages on the web server and use SQL Server only for data
> retrieval/update.
>
> TAKE A LOOK AT MICROSOFT PATTERNS & PRACTICES
>
>
.

Relevant Pages

  • .net 2.0 DataList security
    ... Being a classic .asp programmer I'm very fond of the idea of using the drag ... server to our database SQL Server 2000 server (which is on a different ... each user that accesses the data to our SQL Server database. ... I guess I'm not too clear on the back end things with this DataList control ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: IIS6 - URLScan and MaxQueryString
    ... ALL of the SQL keywords I was searching for, ... I need to keep this from happening while I am finishing fixing the ASP ... I upgraded to URLScan 3.0 (which of course uses ... injection requests, and assuming you are using SQL Server, just deny SELECT ...
    (microsoft.public.inetserver.iis.security)
  • Re: Windows authentication to sql server 2000 question
    ... creating an .asp db app using windows authentication to sql server in that ... other .asp pages that call to the db? ... should I have an immediate database connection to the sql server ...
    (microsoft.public.sqlserver.security)
  • Re: Issue with retrieving large data over web using Stored Procedu
    ... You don't use it to run the stored procedure. ... In other words, start sql profiler, create a new trace and start it, open ... your browser and navigate to the asp page that is giving you the problem. ... while I execute the sp at the SQL Server 2005. ...
    (microsoft.public.inetserver.asp.db)
  • Re: Suchfunktion
    ... Allerdings solltest du mal Google nach SQL Injection ... (Werte aus dem Request sollten nie ungeprüft ... MS MVP für ASP / ASP.Net ...
    (microsoft.public.de.inetserver.iis.asp)