Home Forums SQL Server 2008 SQL Server 2008 High Availability Archieving Data RE: Archieving Data

  • December 14, 2012 at 8:05 pm

    #1568866

    runal_jagtap (12/12/2012)

    The data in the databases are large in amount.. die to which if some one want to retriev report from that db the performance is very poor, the data takes time to come out

    I do regular indexing but still no use..

    I have data for almost 5 yrs in the DB & only 3 months data is required for reporting..

    the scene here is that the columns in the tabkle are not fixed.. some times their is a requirenment to add more columns in it..:w00t:

    Before you spend a lot of time trying to develop and archiving plan, understand that performance problems are because you have a lot of data. It's because you have queries that don't work correctly with a large amount of data.

    Considering that you're also talking about them adding columns, I have to ask, what are the columns for? Are they, by any chance, columns of data based on some timeperiod like day, month, or week?

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)