1. This is from the log of our SQLMAINT.EXE process:
Allocation Discrepancy: Page is allocated but not linked; check the
following pages and ids: allocation pg#=3D90368 extent id=3D90488 =
logical
pg#=3D90488 object id on extent=3D1461580245 (object name =3D Traffic) =
indid
on extent=3D3
Allocation Discrepancy: Page is allocated but not linked; check the
following pages and ids: allocation pg#=3D90368 extent id=3D90488 =
logical
pg#=3D90489 object id on extent=3D1461580245 (object name =3D Traffic) =
indid
on extent=3D3
[and so on for about 10.000 (!) page numbers]
What does it mean, and how do I fix it?? DBCC CHECKDB gives me no errors
at all, everything looks fine.
2. This is from our error.log file:
97/02/26 06:39:53.06 spid11 Fehler: 1105, Schweregrad: 17, Zustand: 1
97/02/26 06:39:53.06 spid11 Kann f=FCr Objekt 'MSProxyLog' in =
Datenbank
'Emerald' keinen Speicher reservieren, da 'default' Segment voll ist. In
Syslogs kann durch Speichern des Protokolls Platz geschaffen werden.
Sonst ALTER DATABASE oder sp_extendsegment verwenden, um die
Segmentgr=F6=DFe zu erh=F6hen.
For those not German-challenged: Cannot allocate space for Object 'xxx'
in db 'yyyy' because the 'default' segment is full .....
The db has a size of 1GB, used space is around 500 MB. What does
'default-segment' mean _exactly_? What am I missing???? How do I fix
it???
Lot's of questions...do you have the right answers???=20
cu, Peter
-
Peter A. Sang
SANG Computersysteme GmbH * Kruppstr. 82-100 * 45145 Essen * Germany
T: +49-201-82020-0 * F:-40 * http://sang.net * mailto:pesa@sang.net
* Microsoft Solution Provider * Intel Systems Integrator *