This is still a problem.
These namespaces span multiple servers, so I think that rules this out? Also, each of the copies will have minor changes (each FTP out adapter will have a different filename prefix, etc). Plus, it sounds super complex for this simple use-case.
edit: But I appreciate the quick response, and mapping sounds really cool otherwise!
I may have realized what I was missing. These "documents" are generated on the fly so I guess you wouldn't be able to reference a static table of document contents. I was led to this by running the following query on the first 15k rows or so.
SELECT DocumentId, HomeCommunityId, RepositoryId, count(AggregationId)FROM HS_IHE_ATNA_Repository.DocumentGROUP BY DocumentId, HomeCommunityId, RepositoryId
These are the numbers of duplicates
ie, only 2 documents were duplicated 8 times. The vast majority only had a single entry. Still, if we extrapolate this out, that's a lot of duplicated data in my opinion. If my math is correct, in this sample, 21% of the documents records are exact duplicates.
I'm not really talking about speed or performance. It just seems strange to me to have a table that stores "document base data" in an event based format. I'm not sure if I'm being clear, so let me see if I can provide a visual
Here is a representation of the way I understand it to work:
And here is what I would expect to see:
Am I missing something?
We can add HIE tag, would you please point the related articles and questions?
This would be great, thanks. I can start a topic eventually with links to posts that should be tagged, but probably not today. Although, it would be really nice if community members could tag posts freely.
I'm actually a spambot designed to get responses. Someone just pointed me at the wrong domain.
But that's not inefficient?
So can you answer the question: Does this mean that if the same document was requested 1,000 times that there will be 1,000 entries for it in the .Document table?
I use this a lot as well, but I really wish it could magically search across our kajillion different HealthShare servers/namespaces. :(
Looks like it's the .indented class. It adds a left margin of 44px to each child comment. If it could somehow only be applied to the first level comment I think that would be ideal. The compromise is that we lose multi-threaded conversations, but yet again, I have to point to Stack Overflow. I think we would adapt pretty well.
Log in or create a new account to continue