Hi,We're building a reporting system in C#. The data source will be file feeds that will be imported into a SQL Server 2008 DB via bcp ( SSIS is not an option as its use is unauthorised by our client).Ideally we'd like to have some sort of FileWatcher, so as soon as the files arrive we trigger the bulk upload. We think that a possible option is to have a C# component hosted by a Windows Service that would be watching the "incoming" folder and would invoke the upload process as the file arrives.We can either have a separate process to do the bulk upload or doing it in the same one but using background threads. What are your thoughts on this?If we've got separate processes (windows services), we'd think of using Rhino ESB - Files arrive, then send a message to the other process so that it can import it into the DB.When all the files have been imported, then another process would perform some calculations off that data and generate the report.Does above make sense or is too overengineered? Another option would be using a single process and then leverage multithreading programming to process multiple files at the same time.Regards.
Sorry about the confusion, let me try to rephrase
:-)
We've got a web app to visualize reports for a given date. In the meantime the feeds for a new date are available, so we have to import them but this process takes over an hour. In the meantime the users might still be viewing reports for an older date. Would you have the import logic running in the same application server on a backgroud thread?
Hope it's a little more clear now.
Regards.
--To view this discussion on the web visit https://groups.google.com/d/msg/rhino-tools-dev/-/z2Azm_5-67MJ.
You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group.
To post to this group, send email to rhino-t...@googlegroups.com.
To unsubscribe from this group, send email to rhino-tools-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.