Viewing 15 posts - 931 through 945 (of 994 total)
There aren't any errors in the output you posted. Can you post the complete output from your DBCC CHECKDB job?
September 27, 2007 at 9:43 am
If you shrink the data file then you're going to fragment your indexes, guaranteed. What you can do is shrink per file with the TRUNCATEONLY option or rebuild the indexes...
September 25, 2007 at 11:51 am
Very interesting - I'm sure its because the DB used to be master. The whole way of storing database metadata changed in 2005 and I'll bet there are some hard-coded...
September 24, 2007 at 1:39 pm
My guess is that someone took a copy of master at some point, moved it to your database's location and attached it under a different name. No database can be...
September 24, 2007 at 8:57 am
How are you trying to restore the database?
What happens if you try to restore it using T-SQL?
September 24, 2007 at 8:53 am
The problem is that they detached the database while it was suspect. Suspect means that recovery could not run for some reason. When you attach a database that has not...
September 23, 2007 at 12:02 pm
Can you do the following and let me know the output you get?
ALTER DATABASE PIS SET ONLINE -- this should try to run recovery, fail and put the database into...
September 19, 2007 at 11:49 am
Well, you have at least one corrupt page in the database that's being hit during recovery. This means you can't access the database unless you put it in emergency mode...
September 18, 2007 at 11:20 am
There will definitely be a SQL Server 2008 Express Edition.
September 12, 2007 at 7:24 pm
This is almost certainly a bug in DBCC CHECKCONSTRAINTS - please contact Product Support (http://support.microsoft.com/sql).
Thanks
September 12, 2007 at 7:12 pm
Your sysindexes table is corrupt. From the call stack in the dump, its failing trying to delete a statistics blob column in sysindexes. You should run DBCC CHECKDB to find...
September 12, 2007 at 7:10 pm
Looks like you've got some corruption which is causing the server to misbehave. What's the output of "dbcc checkdb (yourdb) with all_errormsgs, no_infomsgs"?
September 12, 2007 at 7:07 pm
The only way for you to fix this is to restore from a backup as this type of system table corruption won't be fixed by CHECKDB in SQL 2000 (which...
September 12, 2007 at 7:04 pm
This is bad advice - if the non-clustered indexes are enforcing constraints, dropping them allows operations that could break the constraint and then you wouldn't be able to recreate the...
September 12, 2007 at 7:00 pm
That's terrible advice. You're advocating always choosing to lose data rather than restore from a backup. Why take backups if you're happy running repair?
Unless you have serious downtime constraints and...
September 12, 2007 at 6:58 pm
Viewing 15 posts - 931 through 945 (of 994 total)