none
sys.query_context_settings RRS feed

All replies

  • Hi Sakurai_db,

    Suspects the statuses 0x0400, 0x0484 are the sum of the above mentioned other statuses.

    Eg:

    0x0400 --> 4 times (0x100 - query in context of row-level security predicate).

    0x0484 --> 4 times (0x100 - query in context of row-level security predicate) and (0x80 - encrypted query) and (0x4 - internal query).

    Please mark this as answer if it solved your issue. 
    Please vote this as helpful if it helps to solve your issue. 

    Thanks,
    Arulmouzhi

    Monday, September 2, 2019 7:29 AM
  • what I suspecting is

    0x04xx  << should be default

    0x400 << regular query

    0x484 << Encrypted query +  internal query  

    Monday, September 2, 2019 3:38 PM
  • I agreed with Arylmouzhi.

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Tuesday, September 3, 2019 8:44 AM
  • there is no row-level security over there . and how come 4 times?
    Tuesday, September 3, 2019 7:03 PM
  • Hi Sakurai_db,

    Trying to help on predication's.

    Already given possibility 1. Here posted possibility 2.

    Please check/read this explanation again.it gives some hint.

    'Bitmask field that indicates type of query or context in which query was executed. 
    Column value can be combination of multiple flags (expressed in hexadecimal):'

    Now check below things:

    0x0   (hexadecimal)   - 0(decimal)   - regular query (no specific flags)
    0x1   (hexadecimal)   - 1(decimal)   - query that was executed through one of the cursor APIs stored procedures
    0x2   (hexadecimal)   - 2(decimal)   - query for notification
    0x4   (hexadecimal)   - 4(decimal)   - internal query
    0x8   (hexadecimal)   - 8(decimal)   - auto parameterized query without universal parameterization
    0x10  (hexadecimal)   - 16(decimal)  - cursor fetch refresh query
    0x20  (hexadecimal)   - 32(decimal)  - query that is being used in cursor update requests
    0x40  (hexadecimal)   - 64(decimal)  - initial result set is returned when a cursor is opened (Cursor Auto Fetch)
    0x80  (hexadecimal)   - 128(decimal) - encrypted query
    0x100 (hexadecimal)   - 256(decimal) - query in context of row-level security predicate

    If you use bit wise AND operator like 'select 'columns' from 'table' where status&400=status'.

    It may be something like:

    0x0400 - --(16,128,256)
    0x0484 - --(4,32,64,128,256).

    Please mark this as answer if it solved your issue. 
    Please vote this as helpful if it helps to solve your issue. 

    Thanks,
    Arulmouzhi


    Tuesday, September 3, 2019 8:23 PM
  • why 0x0484 / 0x400 don't have to convert to decimal first before your calculation below?

    0x0400 (hexadecimal) - --(16,128,256) (decimal)
    0x0484 (hexadecimal)- --(4,32,64,128,256) (decimal)
    Wednesday, September 4, 2019 12:45 AM