Performanence very slow after migrated database from 2000 to 2008 sql

  • Users are facing slowness issue after restored database from 2000 to 2008 sql server, they are gernerating report in crystal

    it takes 5 minutes in SQL 2000 physical server.

    But after migrated to VM machine sql 2008 with 80 compatilablity , but report gerneration almost takes 3 hours.

    Could you nyone help on this...

    what is cause of slowness crystal report generation

    BR,

    Jerry

  • solomon.jernas (6/24/2016)


    Users are facing slowness issue after restored database from 2000 to 2008 sql server, they are gernerating report in crystal

    it takes 5 minutes in SQL 2000 physical server.

    But after migrated to VM machine sql 2008 with 80 compatilablity , but report gerneration almost takes 3 hours.

    Could you nyone help on this...

    what is cause of slowness crystal report generation

    BR,

    Jerry

    Did you force an update of statistics after the migration? Also, what are the initial size and growth settings for TempDB?

    And why on this good green Earth would you stick with the SQL Server 80 compatibility?

    --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)

  • You should also be sure your VM has resources. A database server VM is not like some other file server, print server, etc. VM. This needs more resources, more minimums, with fewer guests on the main host.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply