Msg 2540

Msg 2540, Level 16, State 1
Allocation Discrepancy: Page is allocated but not linked;
check the following pages and ids: allocation pg#=614144
extent id=614392 logical pg#=614395 object id on extent=8
(object name = syslogs) indid on extent=0
I forgot to ask what the ramifications are if I migrate
to SQL 2000 with this message still occurring.Jim,
Always fix such problems if you can.
If all of these pages are for syslogs (ie, the transaction log) then life
might not be too bad if you migrate. But I cannot say for sure.
What I would do.
1 - Backup the database
2 - Restore the database backup to a different database, e.g.
mydatabaseRestore
3 - Run the fixes on the second database and observe the results.
Russell Fields
"Jim" <anonymous@.discussions.microsoft.com> wrote in message
news:06e601c3b399$e5d9cbd0$a101280a@.phx.gbl...
> Msg 2540, Level 16, State 1
> Allocation Discrepancy: Page is allocated but not linked;
> check the following pages and ids: allocation pg#=614144
> extent id=614392 logical pg#=614395 object id on extent=8
> (object name = syslogs) indid on extent=0
> I forgot to ask what the ramifications are if I migrate
> to SQL 2000 with this message still occurring.