Topic
2 replies Latest Post - ‏2013-05-13T06:22:23Z by MARQ
SystemAdmin
SystemAdmin
483 Posts
ACCEPTED ANSWER

Pinned topic Records affected limit

‏2013-04-02T15:12:05Z |
We have discovered that Guardium 8.0p140 with STAP on MSSQL has limit of number of returned records. If we run select that return more than 116276 records, Guardium shows -2 as # of returned records.

Below that value it shows correctly. Do you know anything about that limitation? I have opened a case and support claims that this is normal behaviour and to fix it we have to open an RFE. There is a limitation of no of packets analyzed for returned results.

We have tried to change the setting max_tds_response_packets to max level, but without any results.

Frankly speaking it is strange and we have security gap if someone in one query will have more than 120 th. records without any alert on sesitive data. This value seems to me low
MarQ
Updated on 2013-04-03T16:27:01Z at 2013-04-03T16:27:01Z by KRZ
  • KRZ
    KRZ
    51 Posts
    ACCEPTED ANSWER

    Re: Records affected limit

    ‏2013-04-03T16:27:01Z  in response to SystemAdmin
    Hi,
    Did you restart the inspection engine? You need to do that before the change to take effect.
    According to development, it's not a hard limit, and there are 3 related parameter which you can change using the store commands.

    MAX_RESULT_SET_SIZE INTEGER
    MAX_RESULT_SET_PACKET_SIZE INTEGER
    MAX_TDS_RESPONSE_PACKETS INTEGER

    Hope this helps.
    Kathy
    • MARQ
      MARQ
      4 Posts
      ACCEPTED ANSWER

      Re: Records affected limit

      ‏2013-05-13T06:22:23Z  in response to KRZ

      In fact, these settings have limits and the problem is that MSSQL is not sending number of records affected like Oracle does and Guardium box has to count them. There is a limit and we have to monitor "-2" value as it indicates that the limit has been reached.

       

      MarQ