October 24, 2025 at 12:45 pm
Hi when i think of server hops , i think of how kerberos assists with credentials from server to server thru what i think are called sids so that the last server knows the credentials of the account that initiated a request/query.
we'll be talking soon about a need to get data from s4 hana sap (in)directly to sql server. sql server would be the requestor. right there in the middle is a mysql server from which we already get unified s4 and other erp sales data thru a mysql connector installed on our sql server. Our partner who owns the mysql server has created unified views over mysql tables hydrated from s4 data and other erps. We use a linked server to tap into that unified view.
we face a need to get something more like a once daily, lives for only 24 hrs, ods dataset from s4. I mentioned to my peers that it would seem like overkill for a view over a layer of mysql tables for such a dataset. For the AR app we would use this for, we tap right into the 10 or so (and growing) erp's whose AR snapshot we are interested in once daily. Having 2 layers for s4 seems silly and would introduce additional complexity like "when did mysql refresh?", "where do we look for problems?" etc.
we'll start talking about options. one is cdata's s4 connector on our sql server bypassing mysql. Another may be just installing what is probably the same connector they have on mysql (maybe there is a cost), on our sql server and bypassing mysql. My head gets a little fuzzy when i think maybe mysql can have views that go directly to s4 which we tap into from sql...or some kind of hop from sql to s4 thru mysql.
Can the community comment?
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply