tag:blogger.com,1999:blog-2615703102299902978.post601442997308400892..comments2024-02-03T00:03:10.178-08:00Comments on Glenn Schwartzberg's Essbase Blog: Undocumented SQL Data Load Rule ChangeGlennShttp://www.blogger.com/profile/08532634180859769798noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2615703102299902978.post-23581318388387413242016-05-03T03:52:07.781-07:002016-05-03T03:52:07.781-07:00Gotta love SRs going to development. If nothing el...Gotta love SRs going to development. If nothing else i am happy you have enlightened that 'development' is not code for rubbish bin. <br /><br />I avoid using floats but obviously you get what you're given on a job. Can see this biting many people who wont be so lucky to spot the issue.<br /><br />I still dont really get why you get a different value now though. Is it because SQL Server approximates a float differently to Essbase? I'm on my phone so havent dug into the msdn links in the articleDaniel Willishttps://www.blogger.com/profile/07491703670331386170noreply@blogger.comtag:blogger.com,1999:blog-2615703102299902978.post-85789552976694115642016-04-20T07:50:10.676-07:002016-04-20T07:50:10.676-07:00It gets worse. When HFMEA pushes HFM data to the ...It gets worse. When HFMEA pushes HFM data to the fact table, it uses FLOAT for the data type in that table, not a decimal. So when you load values into Essbase through the SQL Interface, they can get mangled. Anonymoushttps://www.blogger.com/profile/12759231936349695787noreply@blogger.com