InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 19 May 2013 05:01:52 GMT20http://www.sqlservercentral.com/Forums/Topic1064529-149-1.aspxPOWER relies on a FLOAT conversion which, IIRC, has a maximum precision of 15 digits. Here's an article that demonstrates the problem for another function that does a FLOAT conversion...[code="sql"]http://www.sqlservercentral.com/articles/T-SQL/71565/[/code]Tue, 15 Feb 2011 16:08:25 GMTJeff Modenhttp://www.sqlservercentral.com/Forums/Topic1064529-149-1.aspxIt's probably a floating point issue. It looks like you're using floating point numbers (they have decimal places), instead of integers. Shouldn't affect whole-number calculations, but it may in this kind of case.Tue, 15 Feb 2011 14:14:42 GMTGSquaredhttp://www.sqlservercentral.com/Forums/Topic1064529-149-1.aspxI was just trying to load up the largest BIGINT, 9,223,372,036,854,775,807, by using the POWER function (2^63) - 1. When plugging in "2 raised to the 63," the returned value is 9,223,372,036,854,775,800 and not 9,223,372,036,854,775,808 as I would expect (prior subtracting 1 to get the largest allowed BIGINT). SELECT POWER(2., 63.) - 1.When obtaining the largest INT value by raising to the power of 31, I get the expected results. SELECT POWER(2., 31.) - 1.This a known issue?Tue, 15 Feb 2011 13:21:01 GMTjon-230788