SQL 2000 vs 2005, Key differences

Posted on 2007-10-09
Last Modified: 2008-02-01
Used Ms SQL 7 and SQL 2k.
Now we have some performance issue and the table has grown.
Our total DB size is 10 GB till now and next year may 11 GB. (100 users)

Question is,
If we upgrade to SQL2005 what benefit will we get apart from
security, relibility, scaleablity.
looking some professional answers from exprets........
Question by:imran786
    LVL 14

    Assisted Solution

    You have added analysis tools and advanced trace...and more the indexing is much better than in the previous versions...
    LVL 142

    Accepted Solution

    in your situation, you might be able to benefit from the table partitioning, splitting large tables into parts, giving you performance boost as queries do not need to run on the entire table/index all the time...
    LVL 7

    Assisted Solution

    Adding to the fellow experts comments you can get use of functions like 'offset' and 'limit'
    For your Knowledgebase
    LVL 8

    Assisted Solution

    you also have partitioned tables, they work same as the partitioned views in sql server 2000, but they are easier to design and create when you look from a developers point of view.
    LVL 8

    Expert Comment

    thanks for warning angelIII, it was intended to keep the answer local as it was more preferable last I was using EE. I'll keep this in mind for the future responses.
    LVL 8

    Expert Comment

    greetings imran786,

    MS has a document on the key differences at :

    But you're probably looking for a review from a user perspective. You can find two different reviews from a DBA's and a developer's perspective here :

    LVL 8

    Expert Comment

    btw, you'll need to register to read the articles on =)

    thanks for the info, angel.
    LVL 142

    Expert Comment

    by:Guy Hengel [angelIII / a3]
    you are welcome.
    glad you understood this in the right way!
    LVL 1

    Author Comment

    Thanks everybody,
    Comparision between 2k & 2k5 is clear now.
    Issue is in performance.
    "splitting large tables into parts" is almost already done.
    I will also read there source article mention in above.
    Any other point is required to trace the reason of slowness.

    Featured Post

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    Join & Write a Comment

    Suggested Solutions

    Entity Framework is a powerful tool to help you interact with the DataBase but still doesn't help much when we have a Stored Procedure that returns more than one resultset. The solution takes some of out-of-the-box thinking; read on!
    This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
    Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.
    Via a live example, show how to shrink a transaction log file down to a reasonable size.

    745 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    15 Experts available now in Live!

    Get 1:1 Help Now