caching table data

[Justin]

I'm involved in this localization project, and part of the process is
taking the english content out of the pages and storing them in the db
as key/value pairs (which we call tokens).

Would be any performance problem if all of the tokens were stored in
one table, for each language. Say there’s 1000 Tokens, and there’s 50
languages supported, then that would be 50000 entries. It's hard to
guess how long each string will be... Ok, that’s not very big, but
what if we were to load that up in the application scope, so it would
be easily accessible (maybe in a dictionary object for each locale).
Do you forsee any problems in that? Or does ASP offer some other
caching mechanism for this?

As always, TIA

[Aaron [SQL Server MVP]]

50000 rows is nothing for a SQL Server database to handle. Queries should
be efficient as well, given proper indexing techniques.

--
http://www.aspfaq.com/
(Reverse address to reply.)


"Justin" <ng@NO_SPAMmaritimeNO_SPAMsource.ca> wrote in message
news:ij********************************@4ax.com...

I'm involved in this localization project, and part of the process is
taking the english content out of the pages and storing them in the db
as key/value pairs (which we call tokens).

Would be any performance problem if all of the tokens were stored in
one table, for each language. Say there’s 1000 Tokens, and there’s 50
languages supported, then that would be 50000 entries. It's hard to
guess how long each string will be... Ok, that’s not very big, but
what if we were to load that up in the application scope, so it would
be easily accessible (maybe in a dictionary object for each locale).
Do you forsee any problems in that? Or does ASP offer some other
caching mechanism for this?

As always, TIA