I'm currently working on developing a windows service which will be deployed to all the workstation within the company. The purpose of the service is to collect various statistics and record them in a central location.
for the first iteration, the service is doing direct call to SQL to record the every time there is data to record. Testing it on about 120 workstation told me that it is not a good idea and won't scale.
Can someone recommend an alternative strategy for collecting the data in question which won't overload the database server? This will be deployed to about 2000 machines.
I'm working with C#.
Thanks.
Just answering to wrap up the question. Here is how I ended up implementing it.
Data Collection
Data Parsing
The reason I implemented it this way is to: