I'm working on a project with an enterprise architecture and named the history provider "SplitHistory" with a type "Tag History Splitter". I tested it and was pleased to see that the system.tag.storeTagHistory function stores data in both historian databases when I specify "SplitHistory" as the history provider parameter. I would really like to see a similar scripting function that would allow historical data to be updated so that I don't have to develop code to determine which partition table to update and so that I don't have to execute my custom code twice - once for each database connection comprising the "SplitHistory" history provider.