Hello all,

A recent project of mine requires a real-time view of a data queue so the user can see, with a lag of preferably no more than 3 seconds, what all the users connected to the SQL Server database are doing.

What I'm wondering is, is the TableAdapter.Fill command at all suited to that? Could I get away with calling .Fill() every 3 seconds, or would that result in a rediculous amount of network traffic? There are 3 tables I'd need to Fill, with (on average) 7 fields per table, and (again, on average) 30-40 records in each table.

Alternatively, would I be better off setting up a flag mechanism of some description? ie. all the clients continually check for the flag and only call .Fill() when it spots it. Would it be better to continually call .Fill() on a 1record-1field table, looking for it to change to true? Or even continually use File.Exists() to look for a flag file on the network?

How would you solve this problem?

Thanks,
Qu