So far, the only approach that may be feasible is to set up a reverse proxy in a cloud service (such as AWS or Azure) to the client's SQL Server database. Then I should be able to connect the SQL Server connector to the reverse proxy as the endpoint.

Reposting this question in a different way to see if anyone has done this.

Ugh. no not the correct reply. In my test sandbox I do not have the "Profile-Snapshot..." dataset either.     I thought perhaps having two merge polices with the same name was an issue.  Not sure that matters.  We see the merge data when browsing the profiles, just no summary data for the dashboard....

Thanks Danny.  No there is no "Profile-Snapshot..." dataset.  We have a segment process running later and will see what happens tomorrow.  I just have to think there is a simple detail I missed.  Like maybe in an API call mistakenly set a flag to disable the dashboard.

It does make sense.  Very few companies with have ALL necessary data curated and enhanced with all required and potential analytic attributes for identifying segments.  Moreover, the speed at which attributes can be created in query service is likely faster than the technical investment to do at the...

This is to update the original question given the 29 Sept 2021 release.  If it works as described it will suffice for updating datasets and, thereby, updating the profile.  There are methods defined to set the upsert tag as true on datasets already enabled for profile. This is a much better solution...

@maggod Your solution is what I had started working on. That way each update to the subset of columns can simply replace the old record. The Real-Time profile then gets updated with the new values. I am just hoping there is a way to UPDATE a record without having to specify all the attributes and re...