Professional Web Applications Themes

Commit Control - Microsoft SQL / MS SQL Server

My company is porting some software that we have running on Oracle and DB2 to SQL Server. For our big batch programs(Microfocus COBOL) we have a transaction Commit frequency that is controlled by a data variable on a table. We don't see any performance difference, i.e. elapsed job time, when running these programs (they do loads of indivual inserts, deletes, updates etc. pretty complicated stuff) with a Commit frequency of 1 or 500. On the other databases optimising the commit frequency has a massive impact on program performance. Is this what I should expect from SQL Server or am I ...

  1. #1

    Default Commit Control

    My company is porting some software that we have running
    on Oracle and DB2 to SQL Server.

    For our big batch programs(Microfocus COBOL) we have a
    transaction Commit frequency that is controlled by a data
    variable on a table.

    We don't see any performance difference, i.e. elapsed job
    time, when running these programs (they do loads of
    indivual inserts, deletes, updates etc. pretty complicated
    stuff) with a Commit frequency of 1 or 500.

    On the other databases optimising the commit frequency has
    a massive impact on program performance.

    Is this what I should expect from SQL Server or am I
    missing something ?

    Have I posted this to the right forum ? I'm pretty new to
    SQL Server so wasn't sure which one was best.

    Any help much appreciated

    Marco
    Marco Guest

  2. #2

    Default Re: Commit Control

    Marco (Marco_Franchilbss.com) writes:
    > For our big batch programs(Microfocus COBOL) we have a
    > transaction Commit frequency that is controlled by a data
    > variable on a table.
    >
    > We don't see any performance difference, i.e. elapsed job
    > time, when running these programs (they do loads of
    > indivual inserts, deletes, updates etc. pretty complicated
    > stuff) with a Commit frequency of 1 or 500.
    >
    > On the other databases optimising the commit frequency has
    > a massive impact on program performance.
    >
    > Is this what I should expect from SQL Server or am I
    > missing something ?
    Very difficult to answer, since I know nothing about your application
    and what is doing. But there are certainly situations where the
    commit frequency matters in SQL Server, for instance when bulk-loading
    data. But that's bulk-load. With regular DML statements it may not
    have the same importance.

    --
    Erland Sommarskog, SQL Server MVP, [email]sommaralgonet.se[/email]

    Books Online for SQL Server SP3 at
    [url]http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp[/url]
    Erland Sommarskog Guest

Similar Threads

  1. rollback or commit?
    By kt03 in forum Coldfusion - Getting Started
    Replies: 6
    Last Post: October 25th, 08:27 PM
  2. database commit
    By KJLTerry in forum Coldfusion Database Access
    Replies: 1
    Last Post: March 4th, 09:12 PM
  3. Commit on closing connection?
    By Ralf Assmann in forum IBM DB2
    Replies: 3
    Last Post: September 25th, 06:54 AM
  4. Commit Control - forgot to mention
    By Marco in forum Microsoft SQL / MS SQL Server
    Replies: 0
    Last Post: July 4th, 10:53 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139