Post reply

Query against partitioned tables dont return all results

  • February 21, 2014 at 3:43 pm

    #283826

    Hello

    I have a database with lets say 4 tables, each have a partition by "region" some are bigger than others but it serves the business needs

    the tables have around 100 million rows each

    We use Sql server 2008 R8 CU 10, 16 cpus, 192gb of ram

    An external user is running a query against those MS management studio, the query is asking for data from all regions but he reports that it only returns data for the smaller one and then says that the query executed successfully, he send me the query on on my side and on my side it returns all the data but it is first returning the data that he mentioned and after a few minutes all the others

    Have anyone seen something like this? I am at a loos on how to solve something that I can't reproduce

    I even rebuild all the indexes from those tables

    Thanks in advance

  • February 21, 2014 at 4:13 pm

    #1691307

    Sounds like a data, network, or request timeout.

    What you see is what's called 'firehosing'. Basically the system starts returning data even though it's not finished getting all of it so you can start sampling and looking at some of the data.

    My primary guess is that he's got a network timeout happening somewhere, particularly if it takes a few minutes between the initial data shipment and the rest of the data being returned.

    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
    Twitter: @AnyWayDBA

  • February 26, 2014 at 7:34 am

    #1692275

    That is what I suspect, but what I do not understand is why the management studio says that the query ended succesfully...

  • February 26, 2014 at 9:56 pm

    #1692525

    ricardo_chicas (2/26/2014)

    That is what I suspect, but what I do not understand is why the management studio says that the query ended succesfully...

    Time to turn the tables. Ask him if you can RDC into HIS machine to verify the problem. 😛

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 4 posts - 1 through 3 (of 3 total)

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