Forum Replies Created

Viewing 15 posts - 706 through 720 (of 994 total)

  • RE: Database Status SUSPECT

    Hmm - I don't see anything at all harsh in what I said - hi - please- thanks.

    What are you taking as harsh Robert? I believe you're mistaking directness...

  • RE: I/O error (bad page id)

    823s are always caused by a problem in the IO subsystem - something underneath SQL Server. I've never seen a case of a SQL Server 2000 corruption causing an...

  • RE: I/O error (bad page id)

    Don't drop the databases - the restore may fail and then you're left with nothing. Restore to a different database name in case there are problems with the backups.

    Yes, of...

  • RE: I/O error (bad page id)

    A reboot isn't going to fix anything - these are corruptions in the database files on disk. The only way for you to repair without losing data is to restore...

  • RE: Question of the Day for 02 Feb 2007

    Both the right answer and the explanation of the right answer are technically incorrect here.

    See http://www.sqlskills.com/blogs/paul/2007/10/04/InsideTheStorageEngineIAMPagesIAMChainsAndAllocationUnits.aspx for the correct explanation.

    Thanks

  • RE: Changing Recovery model from FULL to Simple

    Absolutely agree.

    If you don't want point-in-time recovery, don't use the FULL recovery mode - you don't get any other gain from using FULL. In that case, just use SIMPLE.

    If you...

  • RE: Fragmentation on partitioned tables

    oh - I didn't mean those were the only things that could cause fragmentation. Insert and deletes will cause fragmentation too, depending on their pattern and position within the index.

    As...

  • RE: Truncate Table

    Hmm - dropping the table is the fastest way as it logs the least and doesn't take any locks, compared to truncate table. I think that was a bad question...

  • RE: Fragmentation on partitioned tables

    Here are some quick tips for you:

    - reorganizing an index will never update stats - the operation doesn't have a complete view of the index so can't update stats....

  • RE: Lock escalation

    It depends how many rows you're deleting and whether you've changed the default lock escalation behavior with any trace flags. The default threshold for when escalation can occur (not guaranteed...

  • RE: SQL 2005 Data corruption issue

    Can you set one of the user DBs to not auto-close and then run CHECKDB on it twice? I want to see if it succeeds or not.

  • RE: SQL 2005 Data corruption issue

    I haven't run CHECKDB on SQL Express for a long time so just for my peace-of-mind I ran CHECKDB on master, model, and msdb on an Express instance - it...

  • RE: SQL 2005 Data corruption issue

    And just to be sure, you could successfully run CHECKDB on master, model, msdb the day before? No crashes?

    Are the user databases set to auto-close?

  • RE: SQL 2005 Data corruption issue

    The only thing I can think of is that something crashed and caused a hidden snapshot to stay around. In that case another hidden snapshot cannot be created. If this...

  • RE: SQL 2005 Data corruption issue

    How much free space is there on the drive where the database is stored?

    Did you move the databases at all?

    Something has to have changed between when it worked and when...

Viewing 15 posts - 706 through 720 (of 994 total)