|
|
Posted by Erland Sommarskog on 11/24/05 11:56
Paul (paulwragg2323@hotmail.com) writes:
> I have not managed to resolve this problem yet, this is not a huge
> priority as this does not happen except for with this particular
> database. It does not appear to happen for the customer at their site
> so seems to be something that has either occured when we restored their
> backup to our environment, or a specific issue with the copy of the
> database we received from them (although this is the third copy we have
> had that has exhibited this behaviour).
>
> Do you have a similar problem?
No, this is completely alien to me.
So, you say that there is a common path for all these databases where
this happens? It's always a copy from the customer's production environment
that bails out when you restore into test and you run this standard routine
there?
Hm, could there be some sort of corruption in that database that exhibits
only after a restore?
Did you run DBCC on the database?
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|