use master
select * from sysdatabases
I get:
(6 row(s) affected)
Server: Msg 220, Level 16, State 1, Line 1
Arithmetic overflow error for data type smallint, value = 42840.Trev@.Work (no.email@.please) writes:
> In EM that is, in QA if I use:
> use master
> select * from sysdatabases
> I get:
> (6 row(s) affected)
> Server: Msg 220, Level 16, State 1, Line 1
> Arithmetic overflow error for data type smallint, value = 42840.
Oops! I assume that this is the message that you get in Enterprise
Manager?
If you don't have SP3 installed, try to install it. The bug may have been
fixed.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog wrote:
> Trev@.Work (no.email@.please) writes:
>>In EM that is, in QA if I use:
>>
>>use master
>>select * from sysdatabases
>>
>>I get:
>>(6 row(s) affected)
>>
>>Server: Msg 220, Level 16, State 1, Line 1
>>Arithmetic overflow error for data type smallint, value = 42840.
>
> Oops! I assume that this is the message that you get in Enterprise
> Manager?
> If you don't have SP3 installed, try to install it. The bug may have been
> fixed.
No EM said nothing, just didn't list anything. There was nothing under
management either and the backups hadn't run.
I restarted the service and the databases re-appeared. There are some
that I had taken offline, these are now marked as offline/suspect.
SP3a is already installed. I wonder if there's a bug with taking
databases offline?
If I query sysdatabases in QA, it was OK until I included the version
column. The offline dbs had quite high numbers here, now showing 0 in
that column, most are showing 539. I don't know the significance of this
number.|||Trev@.Work (no.email@.please) writes:
> If I query sysdatabases in QA, it was OK until I included the version
> column. The offline dbs had quite high numbers here, now showing 0 in
> that column, most are showing 539. I don't know the significance of this
> number.
That's a version number for the database format. Anything but 539 sounds
highly suspcious.
What happens if you try to bring these databases online?
If these databases are production data, and you don't have a clean backup,
I think you need to open a case with Microsoft. Something appears to be
broken.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog wrote:
> Trev@.Work (no.email@.please) writes:
>>If I query sysdatabases in QA, it was OK until I included the version
>>column. The offline dbs had quite high numbers here, now showing 0 in
>>that column, most are showing 539. I don't know the significance of this
>>number.
>
> That's a version number for the database format. Anything but 539 sounds
> highly suspcious.
> What happens if you try to bring these databases online?
> If these databases are production data, and you don't have a clean backup,
> I think you need to open a case with Microsoft. Something appears to be
> broken.
Hi Erland, thanks for responding.
I brought all the databases online, all now show 539 for the version
except one called "WebCat", this was never taken offline as it's used on
a daily basis, this one shows null :-\.
All databases are backed up daily on a schedule, the webcat one doesn't
matter if it loses data as it's re-created every night anyway (it's just
a catalogue of files on a particular web server). I might just drop that
database and re-create it.|||Stranger still,
Taking a database offline now sets version to null, I can't however take
"WebCat" offline as it says it's in use (it isn't according to process
info), this is the one where version is already null.|||Trev@.Work (no.email@.please) writes:
> Taking a database offline now sets version to null, I can't however take
> "WebCat" offline as it says it's in use (it isn't according to process
> info), this is the one where version is already null.
I have no idea what is going on with WebCat. I guess the reason that you
see NULL for the offline databases, is because this number is derived by
actually querying the database file itself, so if the database is offline,
the number cannot gotten hold off.
I checked a little further and found that version is in fact a
computed column:
version AS (convert(smallint,databaseproperty(name,'version') ))
At least here we see the source for the conversion error you had.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||I have had this issue several times, and discovered a post from Dan
Carollo in 2002
that led me to the fix.
http://groups-beta.google.com/group...728290bf2776908
Perhaps the version for WebCat got corrupted and if you run the command
in QA to bring it back online, it might fix that corruption.
alter database WebCat
set online
That is what I was able to do and Enterprise Manager works again. In
the past, I have just had to reinstall SQL replacing the Master
database which takes forever!
Michelle
No comments:
Post a Comment