Options besides sql dependency?

[prommel]

What are some options to replace sql dependency using sql server with multiple users? I like how sqlDependency works but without some changes to my database I can't determine what was added, modified , or deleted. So when I receive a notification I'm forced to reload the dataset and refresh. While this is not a major problem with a small dataset, as the dataset grows the time required to do this will be come unacceptable. I know one option is to continue using sqldependency and only load the data displayed for the current day on the calendar. So is there any other ways to keep data sync'd in a multiple user environment? Thanks, Paul Some more information: Application is a scheduling program Use sqldependency for notification only Use linq to sql for actual data retrieval

[Mycroft Holmes]

I'll be interested in any responses to this one, I have never worked with SQLDependancy. I insist on minimum recordset size for the UI, any more than about 500 records gets looked at severely and usually the design is changed to meet the requirement. Where I have to load a large volume I often allow the user to make a number of changes and then reload the dataset.

Never underestimate the power of human stupidity RAH