I think MS never intended people to put stuff in there that would require a log backup. CAn't think of an explicit reason why log backups banned though other than...

Jeff, you cannot do a log backup of master even if you have set it to full recovery mode (why do you need that for master?)

I tried it via native...

with recovery is the default, so you do not need to explicitly include it.

To restore to a new name :

restore database newname from disk = 'backup file old database'

with...

ok, I did a select...

sounds very possible, in which case it would be a column likely to be searched on, and therefore worthy of an index

cs (12/15/2008)

---

One more question:

What happens if you run:

select (100000000000000000000000000000000 * convert(numeric(6),(convert(int,((convert(numeric(7,2),[ObservanceTime],126) - 35000.00) * 100.0)) % 1000000)) + 1000000000000000000000000.0 * ([SourceID] % 100000000) + 10000000000000000.0 * ([TargetID] % 100000000) +...

right now I've no idea what that column is used for, its a bought in app used for security monitoring rather...

it definitely is the index that upsets dbcc. I am able to retrieve data to usiing that index (according to query plan)

unfortunately being SLQ 2000 hard to prove if index...

sorry Paul , it don't like numeric_roundabort set on -

'DBCC failed because the following SET options have incorrect settings: 'NUMERIC_ROUNDABORT'.

I'll give it a whirl Paul.

Paul, succesfully read whole of table without errors, so I'm going to call it quits and enjoy whats left of my sunday (its 7:30 here).

I'm satisfied data is ok...

cheers paul, I'll give it a try but table has 2.6 million rows so may be a while..........

set ANSI_PADDING,ANSI_WARNINGS,CONCAT_NULL_YIELDS_NULL,QUOTED_IDENTIFIER,ANSI_NULLS on

GO

set NUMERIC_ROUNDABORT,ARITHABORT off

GO

dbcc checktable(observances,3)

gives

DBCC failed because the following SET options have incorrect settings: 'ARITHABORT'.

set arithabort on (so the exact settings used when index created)

and I get:

Arithmetic...

according to MSDN

http://msdn.microsoft.com/en-us/library/aa933138(SQL.80).aspx

SET options were correct for creating index on a computed column, but I cannot get dbcc to run on this index with quoted_identifier set on or off and...

thanks for replying Paul. Are you saying quoted_identifier incorrectly set when index created? Because checkdb fails whether it is on or off when checkdb runs