Post reply

Definition of Duration in profiler and cartesian cross product

  • January 24, 2008 at 9:29 am

    #771365

    It does not include moving results across the network.

    Also Select statement does not "commit" it just reads.

    Where do you run Profiler? On the server or on the client?

    Regards,Yelena Varsha

  • January 25, 2008 at 10:50 am

    #771900

    What I mean is what happens if a user runs a select query that returns a lot of data - will the data set be completely cached on the SQL Server until the query completes before it starts to send the data across the network to the client? Or if not does it start sending to the client while the query is running. And in the latter case if the network connection to the client fails half way through, or the client application crashes or otherwise stops accepting the data, will the SQL continue to run (causing data to queue up at the SQL Server waiting to be sent to the client). And in this case will the query show in Profiler as having completed even if the data hasn't all got to the client?

    http://90.212.51.111 domain

  • January 25, 2008 at 11:13 am

    #771925

    I know that it starts sending to the client while the query is still running, for example try to right-click on the big table, click Open and watch as you already have some results on your client but the query is still running.

    This setting depends on how the MIcrosoft Programmers implemented it. Check out these links:

    For the previous versions:

    http://msdn2.microsoft.com/en-us/library/ms675871(VS.85).aspx

    CacheSize Property (ADO)

    For .NET based versions:

    http://msdn2.microsoft.com/en-us/library/tx1c9c2f.aspx

    Paging Through a Query Result (ADO.NET)

    I think the query is completed in Profiler when it is completed on the server or cancel request was received by the server.

    Regards,Yelena Varsha

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

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