After spending a few days loading data into a database (one
2048Mb data segment, one 1024Mb log segment, each exclusively on
its own device) on a SQLv6.5 (SP3) Server, I got around to
setting up some maintenance tasks w/in SQL Executive, one of
which, among other options, runs SQLMAINT with the -CkAl option.
The allocation error I get (which also appears as a "Msg 2525"
after the "INDID=2" line for 'sysobjects' when I run DBCC
NEWALLOC on either it *or* on a totally empty, "fake" db of the
same spec.s) is "Table Corrupt: Object id wrong; tables: alloc
page 0 extent id=208 l page#=208 objid in ext=14 (name =
sysreferences) objid in page=14 (name = sysreferences)objid in
sysindexes=1 (name = sysobjects)". Any info. which y'all might
have on whether or not this error is significant would be
Given that I had previously created a 1000Mb/512Mb database on
this server and that -CkAl ran clean on it, is it possible that
one data and/or log device cannot be more than a certain size and
that I exceeded one or both max.s? I intend to create another
"fake" db with two 1000Mb data segments (create one 1000Mb, then
extend to 2000Mb) and/or with two 1000Mb data devices in order to
see what happens with a subsequent -CkAl, and I guess I'll apply
SP4 iff neither I nor y'all have come up with a workaround. TIA!
% Peritus Clavis % 425 Park Avenue #12-07 =**= New York, NY
% Machinae Vivit % tel: 212/836-8299 =***= fax:
%%%%%%%%%%%%%%%%%% e-mail: see message header, and tweak!