Forum Replies Created

Viewing 15 posts - 76 through 90 (of 146 total)

  • RE: #VALUE! when exporting report to XLS (only)

    try formatting your value fields in the report before exporting. Use something like "0" or "0.00" in the format field and see if that works

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Table Locks Problem

    The last of the three I got now. Please let me know if you need more info

    Blocked stmt

    (@P1 nchar(12),@P2 float,@P3 float)

    SELECT * FROM JDE_PRODUCTION.PRODDTA.F4941

    WHERE (...

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Table Locks Problem

    here is another:

    Blocked stmt

    (@P1 nchar(10),@P2 nchar(30),@P3 float,@P4 float,@P5 float,@P6 float,@P7 float,@P8 float,@P9 float,@P10 nchar(15),@P11 nchar(2),@P12 numeric(18, 0),@P13 float,@P14 float,@P15 numeric(18, 0),@P16 float)

    INSERT INTO JDE_PRODUCTION.PRODDTA.F57CD100

    VALUES (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P12,@P13,@P14,@P15,@P16)

    BLOCKING STMT

    (@P1 float)SELECT *...

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Table Locks Problem

    Hi - Sorry it took so long. Problem came up now again. You will see the result of the query and that the table select that is blocking has nothing...

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Table Locks Problem

    Will investigate the memory thanks.

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Table Locks Problem

    As far as I know it will then give diff waittime not a lck. Do you know of a way to make sure, accept for the normal perfmon?

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Table Locks Problem

    Here is some screen shots.

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Table Locks Problem

    Actually I am still struggeling to see what the code is that is blocking. I have tried activity monitor and inputbuffer but the system is giving me the same query...

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Table Locks Problem

    Maybe found the problem. The command "DBCC inputbuffer" did not give the correct code that was actualy locking tables. I checked the activity monitor and that session had 4 diff...

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Table Locks Problem

    I ran that query while the locks was in place but the query did not return any information.

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Stored procedure exec taking extremely long

    Yes I fixed the SP and it is working fine now. Are you saying that SQL gets stuck on par sniffing for 3 hours? Thats how long I ran the...

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Stored procedure exec taking extremely long

    I understand that it will take longer to create the exec plan but should it take this long? I have been running the execute SP for 55 min now and...

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Stored procedure exec taking extremely long

    thanks for the replies. I did discuss these points with the developer of the report and they are unable to change the way it works. This is a KRONOS database...

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Stored procedure exec taking extremely long

    CirquedeSQLeil (2/4/2010)


    What does the udf do that could not be done in a stored proc?

    it split a comma delimited string into fields. +- 6 fields.

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

  • RE: Stored procedure exec taking extremely long

    wschampheleer (2/4/2010)


    Here's what I would do:

    - consider adding the missing index that the sqlplan mentions

    - use a temp table #timesheets rather than a table variable @timesheets to see whether that...

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Do not reinvent the wheel.
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Viewing 15 posts - 76 through 90 (of 146 total)