Forum Replies Created

Viewing 15 posts - 15,016 through 15,030 (of 49,552 total)

  • RE: Optimal Database Filesize in Filegroup

    mitch.fh (1/2/2013)


    I think that like the cost of parallelism at one point exceed the benefit there is a "break-even point" for database files.

    Don't make the mistake of thinking that multiple...

  • RE: SQL Server detected a logical consistency-based I/O error

    Please post the full and complete, unedited output of that command (you've left out at least one line, possibly more)

  • RE: Optimal Database Filesize in Filegroup

    mitch.fh (1/2/2013)


    More smaller files or fewer bigger files.

    Unless all those files are on different physical drives, fewer bigger files is better. There's no gain from having lots of little files...

  • RE: Index optimization failed for User databases

    You have a table or index with a - in the name and your code doesn't wrap table and index names in []. You're just going to have to go...

  • RE: Logical consistency error

    Please run the following and post the full and complete unedited output.

    DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

    If you're getting repeated corruptions, there's something wrong in the IO subsystem. Check...

  • RE: Growth in tempdb and more RAM

    Maybe. Depends why TempDB's growing.

    If it's due to hash and sort spille, adding memory may help (optimising queries may help more). If it's due to temp tables and table variables,...

  • RE: Reuilding the index.

    REbuilding indexes is done with ALTER INDEX ... REBUILD. That's all that's needed.

    Was the long query not to identify which indexes needed rebuilding perhaps?

  • RE: Report Processing time too long at 7 mins

    Jeff Moden (1/2/2013)


    GilaMonster (1/1/2013)


    Jeff Moden (12/31/2012)


    The first thing I see (same as what Gail posted) is the HAVING clause which is executed only after all the other code has executed....

  • RE: shrinking database

    Safe. Not usually a good idea, but safe.

    If you decide to shrink, you need to rebuild all your indexes afterwards. Don't shrink as small as possible, shrink to a sensible...

  • RE: SQL Server 2008 - profiler settings

    opc.three (12/31/2012)


    Trace Events will not contain plan_handle. I was talking about Extended Events (XE). XE is a new tracing sub-system introduced in SQL Server 2008 that will eventually replace the...

  • RE: Report Processing time too long at 7 mins

    Jeff Moden (12/31/2012)


    The first thing I see (same as what Gail posted) is the HAVING clause which is executed only after all the other code has executed. I recommend...

  • RE: SQL Server 2008 - profiler settings

    No way to directly do that, the execution plan event does not have duration as a column.

    One way to do this is to first capture procedures running slow and then,...

  • RE: Transaction log back and point in time recovery

    MSSQL_NOOB (12/31/2012)


    SQL Server 2000 - Full database back up at 9:00pm; transaction log backup at 12:00pm.

    Backing up the log once a day? That's useless for recovery. It means you have...

  • RE: Transaction log back and point in time recovery

    MSSQL_NOOB (12/31/2012)


    If the percentage used is averaging around, say 5% BEFORE transaction log backup; does that mean there's just a spike at one point in time of use?

    Maybe. You'd need...

  • RE: Turn off auto-stats at table level in 2005?

    Per-index. Look up Alter Index. The Norecompute setting is the setting you want.

Viewing 15 posts - 15,016 through 15,030 (of 49,552 total)