Limitations on filters ?

[Yash Varma]

Hi,

I have an ASPDB app that I have just increased the filtering on to about 19 fields (many with dropdowns) but now my web server hangs (100% CPU Utilisation) and never comes back to life. I am running the filter against a query and not a table and there are over 1000 records with no filter.

I am running NT 4.0 Server SP4.
The filtering was working but for some reason it is not now. Does anyone know of any limitations to the filtering ? or any suggestions why this may be occuring.

Thanks in advance Yash

[Frank]

Yash,
I'll give you an answer and a story...

Answer: No limit on ASPDB. ASPDB just pass along the SQL statement constructed by the Filter and use it to query the DB.

Story: A guy here has a not so fast portable running NT server and ASP and ASPDB etc... He has a mile long ACCESS query and a zillion tables is invlolved. He ran the ASPDB filter against the query and crashed like you described. Ran and crash again, never came back ! One more time - then we went to lunch. Came back and the data was there !!. Now he ran again and wait.. 17 minutes later, it came back. He then did an experiment and convert the query to a table - ran - took 45 Seconds for the query !!!

You might not have the exact same case, but applying some good database technique would help. Check your query in ACCESS or Enterprise manager (I do not know even what db you are using) to see how many tables are moving with it. Use Views, Store procedures etc. to speed it up. If data is static instead of dynamic, then convert to a table.

Finally, if you have a case that is proven to fail in ASPDB only, then I would like you to make arrangement to send me that data and I'll fix it.

Frank


On 2/9/99 1:12:03 PM, Yash Varma wrote:
> Hi,

I have an ASPDB app that I have just increased the filtering on to
> about 19 fields (many with dropdowns) but now my web server hangs (100% CPU
> Utilisation) and never comes back to life. I am running the filter against
> a query and not a table and there are over 1000 records with no
> filter.

I am running NT 4.0 Server SP4.
The filtering was working but
> for some reason it is not now. Does anyone know of any limitations to the
> filtering ? or any suggestions why this may be occuring.

Thanks in
> advance Yash

[Yash Varma]

Thanks for the advice Frank

I have resolved the problem but it was not the problem that you had suspected. What had happened was I had mapped one particular field twice with the same name and the filtering only crashed when I filtered on that field. After fixing that it works nicely.

I am not sure if this is worth mentioning these symptoms somewhere else in case someone else does the same thing.

regards,

Yash

On 2/9/99 7:18:32 PM, Frank wrote:
> Yash,
I'll give you an answer and a story...

Answer: No limit on
> ASPDB. ASPDB just pass along the SQL statement constructed by the Filter
> and use it to query the DB.

Story: A guy here has a not so fast portable
> running NT server and ASP and ASPDB etc... He has a mile long ACCESS query
> and a zillion tables is invlolved. He ran the ASPDB filter against the
> query and crashed like you described. Ran and crash again, never came back
> ! One more time - then we went to lunch. Came back and the data was there
> !!. Now he ran again and wait.. 17 minutes later, it came back. He then did
> an experiment and convert the query to a table - ran - took 45 Seconds for
> the query !!!

You might not have the exact same case, but applying some
> good database technique would help. Check your query in ACCESS or
> Enterprise manager (I do not know even what db you are using) to see how
> many tables are moving with it. Use Views, Store procedures etc. to speed
> it up. If data is static instead of dynamic, then convert to a table.
>

Finally, if you have a case that is proven to fail in ASPDB only, then
> I would like you to make arrangement to send me that data and I'll fix
> it.

Frank


On 2/9/99 1:12:03 PM, Yash Varma wrote:
> Hi,

I have
> an ASPDB app that I have just increased the filtering on to
> about 19
> fields (many with dropdowns) but now my web server hangs (100% CPU
>
> Utilisation) and never comes back to life. I am running the filter against
>
> a query and not a table and there are over 1000 records with no
>
> filter.

I am running NT 4.0 Server SP4.
The filtering was working but
>
> for some reason it is not now. Does anyone know of any limitations to
> the
> filtering ? or any suggestions why this may be occuring.

Thanks
> in
> advance Yash

[Frank]

Yash,
You mean if we filter Name="Frank" AND Name="Kwong". It'll crash ? even though this is SQL syntax, I'll make a note of that.

Thanks,

Frank



On 2/10/99 4:36:30 AM, Yash Varma wrote:
> Thanks for the advice Frank

I have resolved the problem but it was not
> the problem that you had suspected. What had happened was I had mapped one
> particular field twice with the same name and the filtering only crashed
> when I filtered on that field. After fixing that it works nicely.

I am
> not sure if this is worth mentioning these symptoms somewhere else in case
> someone else does the same thing.

regards,

Yash

On 2/9/99 7:18:32
> PM, Frank wrote:
> Yash,
I'll give you an answer and a
> story...

Answer: No limit on
> ASPDB. ASPDB just pass along the SQL
> statement constructed by the Filter
> and use it to query the
> DB.

Story: A guy here has a not so fast portable
> running NT server
> and ASP and ASPDB etc... He has a mile long ACCESS query
> and a zillion
> tables is invlolved. He ran the ASPDB filter against the
> query and
> crashed like you described. Ran and crash again, never came back
> ! One
> more time - then we went to lunch. Came back and the data was there
> !!.
> Now he ran again and wait.. 17 minutes later, it came back. He then did
>
> an experiment and convert the query to a table - ran - took 45 Seconds for
>
> the query !!!

You might not have the exact same case, but applying
> some
> good database technique would help. Check your query in ACCESS or
>
> Enterprise manager (I do not know even what db you are using) to see
> how
> many tables are moving with it. Use Views, Store procedures etc. to
> speed
> it up. If data is static instead of dynamic, then convert to a
> table.
>

Finally, if you have a case that is proven to fail in ASPDB
> only, then
> I would like you to make arrangement to send me that data
> and I'll fix
> it.

Frank


On 2/9/99 1:12:03 PM, Yash Varma
> wrote:
> Hi,

I have
> an ASPDB app that I have just increased the
> filtering on to
> about 19
> fields (many with dropdowns) but now my
> web server hangs (100% CPU
>
> Utilisation) and never comes back to
> life. I am running the filter against
>
> a query and not a table and
> there are over 1000 records with no
>
> filter.

I am running NT 4.0
> Server SP4.
The filtering was working but
>
> for some reason it is
> not now. Does anyone know of any limitations to
> the
> filtering ? or
> any suggestions why this may be occuring.

Thanks
> in
> advance Yash

[Yash Varma]

Hi Frank,

sorry for not being too clear. But what I meant was if you map names of fields using the MyDb.dbNameMap function and a field is mapped twice then the filter (on the field that is mapped) twice fails and causes the WS to crash.

regards,

Yash




On 2/10/99 6:55:49 PM, Frank wrote:
> Yash,
You mean if we filter Name="Frank" AND Name="Kwong".
> It'll crash ? even though this is SQL syntax, I'll make a note of
> that.

Thanks,

Frank



On 2/10/99 4:36:30 AM, Yash Varma wrote:
>
> Thanks for the advice Frank

I have resolved the problem but it was
> not
> the problem that you had suspected. What had happened was I had
> mapped one
> particular field twice with the same name and the filtering
> only crashed
> when I filtered on that field. After fixing that it works
> nicely.

I am
> not sure if this is worth mentioning these symptoms
> somewhere else in case
> someone else does the same
> thing.

regards,

Yash

On 2/9/99 7:18:32
> PM, Frank wrote:
>
> Yash,
I'll give you an answer and a
> story...

Answer: No limit
> on
> ASPDB. ASPDB just pass along the SQL
> statement constructed by
> the Filter
> and use it to query the
> DB.

Story: A guy here has a
> not so fast portable
> running NT server
> and ASP and ASPDB etc... He
> has a mile long ACCESS query
> and a zillion
> tables is invlolved. He
> ran the ASPDB filter against the
> query and
> crashed like you
> described. Ran and crash again, never came back
> ! One
> more time -
> then we went to lunch. Came back and the data was there
> !!.
> Now he
> ran again and wait.. 17 minutes later, it came back. He then did
>
> an
> experiment and convert the query to a table - ran - took 45 Seconds for
>
>
> the query !!!

You might not have the exact same case, but applying
>
> some
> good database technique would help. Check your query in ACCESS
> or
>
> Enterprise manager (I do not know even what db you are using) to
> see
> how
> many tables are moving with it. Use Views, Store procedures
> etc. to
> speed
> it up. If data is static instead of dynamic, then
> convert to a
> table.
>

Finally, if you have a case that is proven
> to fail in ASPDB
> only, then
> I would like you to make arrangement to
> send me that data
> and I'll fix
> it.

Frank


On 2/9/99
> 1:12:03 PM, Yash Varma
> wrote:
> Hi,

I have
> an ASPDB app that I
> have just increased the
> filtering on to
> about 19
> fields (many
> with dropdowns) but now my
> web server hangs (100% CPU
>
>
> Utilisation) and never comes back to
> life. I am running the filter
> against
>
> a query and not a table and
> there are over 1000 records
> with no
>
> filter.

I am running NT 4.0
> Server SP4.
The
> filtering was working but
>
> for some reason it is
> not now. Does
> anyone know of any limitations to
> the
> filtering ? or
> any
> suggestions why this may be occuring.

Thanks
> in
> advance Yash