Post reply

is there any change in query execution time , when we replace NTEXT with nVARCHAR ?

  • November 1, 2012 at 4:54 am

    #269451

    i have table with lots of NTEXT fields. some of them are rarely used.

    i just replaced ntext with nvarchar. is there any chance to execute my query faster?

  • November 1, 2012 at 5:02 am

    #1554942

    Probably not.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • November 1, 2012 at 6:00 am

    #1554965

    May be it will boost your performance,

    you can create index on varchar which is not possible on ntext.

    but still it depend upon the length of you data.

    -----------------------------------------------------------------------------
    संकेत कोकणे

  • November 1, 2012 at 6:08 am

    #1554968

    sanket kokane (11/1/2012)

    you can create index on varchar which is not possible on ntext.

    You can't create an index on an nvarchar(max), which is the replacement for ntext. Just replacing the data types is unlikely to have a measurable or noticeable impact on performance

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • November 1, 2012 at 6:15 am

    #1554971

    database will flooded with GBs of data in each day .i used to archive data in day wise.

    The actual problem is when querying some thing from huge data , to show it on a web page. then there the problem. Query time out occurs.

    i used indexing .

    I felt the query execution will be slower in querying for some data.?

  • November 1, 2012 at 7:24 am

    #1554993

    Just changing ntext to nvarchar(max) is not going to magically make queries significantly faster. You need to identify what's slow and tune those queries.

    http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/

    http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-2/

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • November 1, 2012 at 7:41 am

    #1555004

    thanx

Viewing 7 posts - 1 through 6 (of 6 total)

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