Hi, Serge:

See my inline comments. Analyzing your business requirements, select a
proper way!

Regards,

Do you know batching, asynchrony and parallel computation with online
compression? See the sample project SocketPro at www.udaparts.com


"calderara" <calderara (AT) discussions (DOT) microsoft.com> wrote

This is faster, but you may need to write code for synchronizing memory
cache and backend database. Also, you may need to lock the memory cache if
you need to access it from different threads. If your memory cache is too
large, maybe this method is not a proper way.

In short, if you can surely synchronize memory cache and backend
database and memory cache is not too large, this way may be preferred.

This way is simpler, but it is slightly slower because a request has to
be sent to a backend database.

HI,

I do not need to keep syncronistaion of memeory with back end database
becasue data which are pushed are configuration data that never change. There
are not live data but more a predifine message structure base on a
configuration.

Whnen a request is coming, I should be abvle to send back message 1, message
2, or message 3 depending on the request...

SO storing in memory mind be ok, but what do you thing culd be the limit
size for this time solution ?

regards

"msgroup" wrote:

=?Utf-8?B?Y2FsZGVyYXJh?= <calderara (AT) discussions (DOT) microsoft.com> wrote in
news:55586CB6-DA81-47CA-AC2F-DD97E6F51B8C (AT) microsoft (DOT) com:

I would store in memory and mirror the data to the database.

Of course it depends on how many alerts your expecting.

BTW, SQL Server 2005 has an notification service which can push database
table changes as events. Might be worth to take a look.

=?Utf-8?B?Y2FsZGVyYXJh?= <calderara (AT) discussions (DOT) microsoft.com> wrote in
news:90F13031-EE74-4746-962B-EBC03899C91F (AT) microsoft (DOT) com:

Memory (RAM) is cheap these days. So you could theoretically store GBs of
data in RAM ;-)

Since you don't need to sync stuff from memory to the database, that makes
your life even easier!

does thsi notification event is present also in sqlexpress 2005 ?

"Spam Catcher" wrote:

Hi, calderara:

For time solution, it mainly depends on your Network latency. To find
the best resultion, you can ping your client from your server. The ping time
is your best resolution you can get.

The max time resultion is your network latency. For LAN (local area
network), it should be less than 0.5 ms (or 500 us). For WAN, it should be
less than 30 ms, which is dependent on ping time from your server to your
client machine.

If you can batch and broadcasting multiple messages in one call like we
do at the site http://www.udaparts.com/document/art...hatservice.htm,
the time resolution can be improved further. If your message is large, you
turn on online compression so that message size is reduced and transferred
at the fastest speed.

Wish the above hint is useful to you.

Regards,

"calderara" <calderara (AT) discussions (DOT) microsoft.com> wrote