Post reply

Service broker not able to cope with many login event notifications ...

  • February 12, 2010 at 3:27 am

    #1117940

    Another improvement I came up with is just because it always uses a fixed column combination to check for existence ..... use a checksum of those columns.

    ALTER TABLE dbo.T_DBA_ConnectionTracker

    ADDFastTrack_CheckSum AS checksum([host_name], [program_name], [nt_domain], [nt_user_name], [login_name], [original_login_name], [client_net_address]) PERSISTED

    GO

    CREATE NONCLUSTERED INDEX X_T_DBA_ConnectionTracker_FastTrack_CheckSum ON dbo.T_DBA_ConnectionTracker

    (

    FastTrack_CheckSum

    ) ;

    And off course alter all queries of the sproc to use this new column.

    It provides a faster access path.

    I've restarted the stress test.

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • February 12, 2010 at 8:56 pm

    #1118387

    Good stuff ALZ, I think that should satisfy my recommendation to improve the discrimination of the Update index.

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.     [/font]    [font="Verdana"] "Performance is our middle name."[/font]

Viewing 2 posts - 16 through 17 (of 17 total)

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