DM.EnterpriseGateway Error: 0 : 2019-02-12T22:31:48.8035781Z DM.EnterpriseGateway d3df4619-cfd0-4044-98c6-b23a97e637ac 99fdd2e7-6c6c-495c-5d97-99e22d710202 MGEQ 99fdd2e7-6c6c-495c-5d97-99e22d710202 30C29923 [DM.Pipeline.Diagnostics] Exception data: DM_ErrorDetailNameCode_UnderlyingErrorMessage = The credentials provided cannot be used for the SapHana source. (Source at glb-hana-102.ghdnet.internal:31015.)
Will SAP be able to avoid falling back on speed to justify the HANA business case? At Sapphire Now Madrid 2012, SAP was proudly citing 18 customers in the 10K club who has improved select processes by 10,000 times with HANA. SAP cited an increase to 26 in the 10K club last week, but is it the best talking point? With Teradata announcing in-memory technology and also boasting 3,000 times speed improvements, database speed will be a commodity sooner than later. The HANA startups I've talked to usually put speed fourth on their list of HANA's appeal, after real-time, predictive/computational features, and ability to "mashup" diverse information sources. Whoever makes the best in-memory business case will win. Sapphire Now 2013 is the ideal time for SAP to do that.
760c119bf3