This cookie is set by GDPR Cookie Consent plugin. The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly. Business Intelligence Business Objects Business Objects Community BusinessObjects BusinessObjects Community IDT Information Design Tool InfoSol Inspired BI Inspired Business Intelligence multi connections Multi-Source Connections SAP Business Objects SAP BusinessObjects Maybe I’ll start using multi-connections in IDT more often. If you have a great use-case you’ve seen for multi-source connections, please share it in the comments below. In classes I’ve taught we’ve had discussions around this topic that I put out to the group up until now without a hit. Although lemmings are cute, my parents whisper is not so much. I’m happy to finally have a use-case for this purpose. The same kind of thing would be seen with work tasks and customer accounts and more. The main dimensions were the invoice number and date which exists in multiple sources for different reasons. I can see this case as useful in many environments. No management of indexing is required since the sources are not joined. Further, the results of the minus query can then be used in the query filter of other queries in the document to get the exact results needed. Although a union is reproducible through merged data providers, minus queries aren’t. You cannot do a combined query in Webi unless the data is in the same universe. For this scenario, this is the perfect solution.
My client needs to run a real-time minus query across multiple data sources. Today I came across a real use scenario that changed my mind. If you combined them at the universe level, although perhaps gaining some ease of use for developers, having to keep up indexing and being limited on SQL are big downsides. But in many cases the merging of data providers in a document means that you could get what you want from two separate universes and not have to deal with the maintenance and performance issues of combining sources. I do, of course, use the multi-source for SAS and SAP BW connectivity, but that is its own use-case.Ĭertainly, there is real-time querying. I hear my parents quietly whispering the lemming song… But this is potentially harmful performance in unnecessarily adding in the federation service use.
After all, performance would dictate single connection with data warehousing from multiple sources.Īnd there is a risk that people will set all data foundations as multi-source because single-source connected data foundations cannot be changed to multi-source connections after creation. I didn’t see the fuss of multi-connections. The idea is that IDT gives us the ability to bring SQL Server data into the same universe as Oracle data, for example. But when IDT came out, I was a little surprised at all the hype given to one of the features – multi-source connections. Information Design Tool (IDT) is a fantastic enhancement by SAP for designing universes. Simplified, I think it was called “The Lemming Rule.” And so, it follows that maybe it was the one rule our parents passed on that they hoped we would follow too. Although sometimes it pays to break that rule, in many cases it is the one rule that we pass on to our kids that we most hope they follow. Sometimes just because you can, doesn’t mean you should.
0 kommentar(er)
