Talk:SAP HANA

"Needs rewrite of Introduction"
I found the introduction here to be a really inaccessible as a native English speaker. Is this just a translation from some other language? The Flesch–Kincaid readability tests in MS Word say the current version has a score of 0.0, and a grade level of 20.1 (typically this should be a score of 60 or higher, and a grade level of 10 or lower to be comprehensible to most people). In addition to this, I think more information should be added up top. I'm get that this is a database of some sort, and maybe a suite of software running on top of the database. But what is it solving? What is unique that makes it different than any of the other database platforms out there (e.g. MySQL or Mariadb)? My guess is this is designed specifically for some niche role, but what role is that: is it for a specific industry, or supporting specific tasks/roles within a company? Or maybe it has some specific behavior that it provides that other databases cannot? Recommend that this be rewritten98.42.11.58 (talk) 19:27, 24 May 2024 (UTC)

"In the cloud"?
VaStanley added a table that had "HANA in the cloud" for May 2012. I added a comment saying this seemed to be a buzzword. A subsequent comment added by that user was: "I thought having the platform in the cloud was pretty impressive. But maybe you can search ever more impressive dates for SAP HANA, I just thought having this section for open contribution would not be a bad idea." Generally discussions should take place on the talk page instead of the content page, so will move here. To be clear, inclusion in the article is not based on what an editor thinks is "impressive", but rather if a reliably source can be paraphrased into giving some actual information on the topic. In this case, we need to explain what this thing is, why it matters, and how it relates to other topics. Saying something is "in the cloud" has no technical meaning, since any software can be "in the cloud" these days. It might have a marketing meaning, if the software is sold as a service instead of as a software product on customer's hardware, or as a computer appliance. However, the citation in this case only says that SAP mentioned both "cloud" and "HANA" in a quarterly report. It says nothing about HANA as a service. The content should be verifiable from the citations. Looking more I find other sources saying there was some announcement in May 2013 about a HANA service offering. That article implies that HANA on Amazon was supposedly supported in 2012, but does not go into details. It looks like that was announced in October 2012, and that is something different again. Perhaps best would be to present this information in prose anyway and then we could explain in a sentence or two instead of just a few jargon terms? W Nowicki (talk) 17:38, 14 October 2013 (UTC)


 * Hi, thank you for moving it here, I am really sorry I did't know this is the right place to post since I just started contributing to wikipedia. And I have to admit, I jumped to the conclusion too fast, I read an article about people using HANA database in the cloud which I found really impressive, and then I tried to find when it started and where I can reference. This Forbes was the earliest came up and I did not read through. The article I really meant was this one: SAP launches cloud platform built on HANA, written by Doug Henschen from Information week.


 * I misdoing this and I will take the row out, paraphrase couple sentences from the article and post in this talk page section before posting it there. Hopefully this sounds ok to you. VaStanley (talk) 02:11, 15 October 2013 (UTC)

Your patience is appreciated: it takes a while to learn the details of the style guidelines. Another detail was date format. As per Manual of Style/Dates and numbers, I was using US-style dates since most of the sources seemed to be from the US, although the company is based in Germany. European dates would have also been acceptable, but probably not worth changing now. We never use leading zeros and prefer to spell out month names to make them unambiguous. A bigger issue was that the row that said "HANA available to the public" in June 2011 was not consistent with the rest of the article nor sources, and not mentioned in the source that was cited. So I went ahead and replaced the table with prose that was paraphrased from the citation or two at the end of each sentence or paragraph. Let me know if anything was inaccurate (sometimes independent sources do not get details right, but so far trying to keep this at a high level. W Nowicki (talk) 17:30, 15 October 2013 (UTC)


 * Thank you so much for taking the step to clean it up. I also really appreciate that you take the time here helping me understand what is going on. I will definitely watch the date format from now on. And I will take a look at how you did with the references and pay really close attention next time. VaStanley (talk) 01:06, 16 October 2013 (UTC)

Neutrality of first paragraph
I added a  to the initial section as it reads like an advertisement for SAP's product. "Exploiting the maximum out of multicore processors" is a subjective claim as is "enabling very fast query execution". Jonnat (talk) 20:21, 29 September 2014 (UTC)


 * Very reasonable in my view. q (talk) 14:25, 13 May 2016 (UTC)

Book
So that readers can be better informed about the future direction of SAP HANA, can we also please add a new section on the publication of the book? Thank you for considering this!

In 2015, SAP Founder Hasso Plattner published a book, co-written with Bernd Leukert, member of the Executive Board of SAP SE, called “The In-Memory Revolution: How SAP HANA Enables Business of the Future,” which describes the capabilities of the SAP HANA technology.

Harper70 (talk) 15:52, 2 October 2015 (UTC)Harper70

Proposal to improve SAP HANA page
The SAP HANA page is far below the standards of other database pages on Wikipedia, even ones that are far less notable. Does anyone have suggestions to improve this page. It looks like this is a stub compared to other pages, and it would be nice to bring it up to a sensible level in line with similar content. q (talk) 00:34, 13 May 2016 (UTC)


 * Note: I've started work to bring the quality up to par with other databases. If you have any feedback or would like to participate please feel free. You can use any other database page as an example of what a proper structure would be. q (talk) 22:05, 13 May 2016 (UTC)


 * Added Database Stub tag to encourage others to build on the content. q (talk) 05:48, 14 May 2016 (UTC)


 * I'm happy to try and add some stuff here when I get the chance, have used HANA at work in the past. Noticed some people talking about the databases wikiproject, below - haven't looked at that in detail yet but can start there when I get round to it. Guidance and feedback welcome - still feel like a wikipedia newbie! Swoophle (talk) 12:18, 26 July 2017 (UTC)

Deletions by User:Seraphimblade
I tend to agree that some of the content should be edited, but wholesale deletions of useful content is the wrong approach in my view to improve the article. Other database articles are far nicer, and with detailed content. We should strive to reach those pages, and not go back to a stub page. q (talk) 17:03, 8 July 2016 (UTC)


 * I agree with the edit to remove fluff and excessive name use. I do not agree with the deletion of technical features. Technical articles on any number of topics include features. I have not reverted the deletion as we're entering edit war territory, but we need to come to a consensus on how to bring up the quality of this article in line with other database articles. q (talk) 01:20, 10 July 2016 (UTC)
 * I won't argue with you a bit on raising the quality. The removals take care of the immediate problem (promotional editing, by, I suspect, employees or PR types), but a lot of our technical articles could use a good deal of work, this one included. As far as features, let's start with trying to move it from a laundry list and see what independent sources consider significant features of the software. From there, we can write a good section on features based on what they have to say about them, without it being sales brochure style stuff. Seraphimblade Talk to me 12:39, 10 July 2016 (UTC)
 * Very fair response. Would you be able to link to a technical feature section that you think is good for reference? Otherwise, I'll do some light googling in the background while I rebuild a database and see if it becomes clear from independent sources. q (talk) 21:29, 10 July 2016 (UTC)
 * I've found some articles that might be usable for it. This one at least touches on the in-memory component, though it's pretty much them and Oracle fighting, so would need to be taken with a bit of salt: This one also focuses on it being in-memory, and that seems to be a recurring theme, so I'm thinking that's the primary thing to focus on:  This one touches on integration with Business Suite, which is probably also worth touching on (it also speaks a bit on lock-in, which we may want to throw in there somewhere):  There's more out there, so I think we can get a well-referenced section there.
 * I've added a couple of sections to the article using those refs. There's plenty of stuff out there on HANA and it's an area I'm trying to learn more about. Will try adding suitable content when I can Swoophle (talk) 17:26, 1 August 2017 (UTC)
 * As to a decent feature section, at least among articles on RDBMS, sadly, no. Looks like a lot of them are in pretty sorry shape. That's kind of unfortunate, given the importance of an RDBMS to just about any major network service out there. I noticed you'd had a bit of activity on the databases Wikiproject, I wonder if there's any chance of getting that going again, or maybe rolling it in as a subgroup of a larger computing project to get some eyes on it? Seraphimblade Talk to me 16:58, 11 July 2016 (UTC)
 * The SAP vs. Oracle stuff all tends to be low value content. I mostly work in open source (openstack), but I have been a consultant working on Oracle, Hana, MemSQL, and many other databases. I'm aware in my head of all the specific details, but that isn't a reference, and outside of documentation a lot of it is just fairly bad from what I've looked through. Example, HANA can be used with Business Suite, as can Oracle and DB2. Lock-in for Oracle and HANA are generally concerning the level of specific code you write for them, stored procedures etc. I understand the nuances here, but I don't desire to try and write this article. I feel like including others and getting more eyes on it is the best way to move forward. A subgroup of a larger computing project sounds like a great idea, I'll have a glance at some of the computing projects and try and find an active one we build with. q (talk) 18:01, 11 July 2016 (UTC)
 * I should add, I am willing to put forth some effort however I don't want to do this alone, and ideally have another article/section that is considered quality to try and conform to. I really wish the template from the Database Project would have taken off, as all of these pages ideally need a template to follow and consistency between them. Each one looks entirely different to each other, with quality all over the board. q (talk) 19:08, 11 July 2016 (UTC)

I am missing notes about ABAP
I am missing the term "ABAP" on the current page. What happens to the current development language? The article currently only mentions nodejs and javaEE — Preceding unsigned comment added by Guettli (talk • contribs) 11:42, 5 December 2018 (UTC)