• Bunny786 (1/22/2015)


    Thanks a lot for reply.

    SQL Server not Shutting down or not crashing ,We have 15-20 developers to access the 30 TB database,Some of the developers are able to connect the database and remaining developers should be in stand by.

    Developers are accessing nearly 100 tables very frequently so i thought if i create schema,File groups or Table partitioning to that tables it will work?

    As you said, you're new to SQL. Having a 30TB database isn't something that newbies or even 15-20 developers can tweak. You need someone that understands SQL Server and databases at a pretty deep level. As Kevin Boles suggested on this thread previously, you need to find a consultant that can come onsite, fix your problems, and educate you in the process.

    As Perry suggested above, SSD's can make a decent improvement but they're not a performance panacea.

    And, if the server isn't shutting down or crashing, why did you post the following in your original post?

    they access some tables and retrieval time is very slow, sometime when they update many records. . [font="Arial Black"]Server is shutting down.

    [/font]

    Don't lie or make stuff up. It's not going to help here.

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