October 26, 2007 at 9:14 am
It's a table like any other table, how you get the data to your user is entirely up to you once you have the data. You could use reporting services, you could use a DTS task to parse out the data and mail it whomever needs to deal with it. You could write some sort of custom application that inspects the left-overs and figures out what's wrong with them and mails them to your users, the possibilities really are only as limitless as your imagination (and perhaps budget) is.
The idea being that you will import more records tomorrow and truncate the staging table first. You want the data changed in your production app, not just on the reporting end of things, right? Once they make the change it gets imported the next time the process runs because the data is now correct. Otherwise they will eventually get so out of synch that the reporting solution won't be reporting anything worthwhile.
Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply