Monday, February 13, 2012

arithmetic overflow error

When attempting to view the properties of a database in SQL Server Management
Studio we are getting an error dialog that states the following.
Cannot show requested dialog.
Arithmetic overflow error converting expression to data type int (Microsoft
SQL Server, Error:8115)
Below is client version info
Microsoft SQL Server Management Studio9.00.3042.00
Microsoft Analysis Services Client Tools2005.090.3042.00
Microsoft Data Access Components (MDAC)2000.085.1117.00
(xpsp_sp2_rtm.040803-2158)
Microsoft MSXML2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer7.0.5730.11
Microsoft .NET Framework2.0.50727.42
Operating System5.1.2600
Server version is 9.0.3054.
The size of the database on disk is in excess of 30TB which, I suspect, is
largely the cause. Any help is appreciated.
Sounds like the db size is the culprit. If so it is most likely a bug and
some poor coding on the developers part. I would post a bug on connect.
www.connect.microsoft.com
Andrew J. Kelly SQL MVP
"mike padula" <mikepadula@.discussions.microsoft.com> wrote in message
news:207536F9-64DF-4937-96C6-7D30C5D920ED@.microsoft.com...
> When attempting to view the properties of a database in SQL Server
> Management
> Studio we are getting an error dialog that states the following.
> ----
> Cannot show requested dialog.
> Arithmetic overflow error converting expression to data type int
> (Microsoft
> SQL Server, Error:8115)
> Below is client version info
> Microsoft SQL Server Management Studio 9.00.3042.00
> Microsoft Analysis Services Client Tools 2005.090.3042.00
> Microsoft Data Access Components (MDAC) 2000.085.1117.00
> (xpsp_sp2_rtm.040803-2158)
> Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
> Microsoft Internet Explorer 7.0.5730.11
> Microsoft .NET Framework 2.0.50727.42
> Operating System 5.1.2600
> Server version is 9.0.3054.
> The size of the database on disk is in excess of 30TB which, I suspect, is
> largely the cause. Any help is appreciated.
|||Thanks Andrew, I posted something on MS Connect about 3 weeks ago. Nobody
seems to have given it much notice quite yet. Nonetheless, I've just edited
it to try to provide some additional information. We're also getting the
error when we try to generate DDL scripts for database objects (tables and
such)...
We also think it's a bug, related to the DB size as we do not get this error
on the same server when using the same client conected to a smaller database.
But, it may not be a "client" problem...because we get the same error when we
run sp_helpdb...that is:
Msg 8115, Level 16, State 2, Line 1
Arithmetic overflow error converting expression to data type int.
The statement has been terminated.
"Andrew J. Kelly" wrote:

> Sounds like the db size is the culprit. If so it is most likely a bug and
> some poor coding on the developers part. I would post a bug on connect.
> www.connect.microsoft.com
>
> --
> Andrew J. Kelly SQL MVP
> "mike padula" <mikepadula@.discussions.microsoft.com> wrote in message
> news:207536F9-64DF-4937-96C6-7D30C5D920ED@.microsoft.com...
>
>
|||You can also call MS PSS. It will cost about $200 or so to get in but if it
is a bug they will refund all your money.
Andrew J. Kelly SQL MVP
"mike padula" <mikepadula@.discussions.microsoft.com> wrote in message
news:98DBE125-4062-4AE7-A294-0B1811FB65C9@.microsoft.com...[vbcol=seagreen]
> Thanks Andrew, I posted something on MS Connect about 3 weeks ago. Nobody
> seems to have given it much notice quite yet. Nonetheless, I've just
> edited
> it to try to provide some additional information. We're also getting the
> error when we try to generate DDL scripts for database objects (tables and
> such)...
> We also think it's a bug, related to the DB size as we do not get this
> error
> on the same server when using the same client conected to a smaller
> database.
> But, it may not be a "client" problem...because we get the same error when
> we
> run sp_helpdb...that is:
> Msg 8115, Level 16, State 2, Line 1
> Arithmetic overflow error converting expression to data type int.
> The statement has been terminated.
>
> "Andrew J. Kelly" wrote:

No comments:

Post a Comment