SSRS timeout

  • agrawal.prakriti

    Mr or Mrs. 500

    Points: 572

    Comments posted to this topic are about the item SSRS timeout

  • Ron McCullough

    SSC Guru

    Points: 63877

    From the question

    under timeout (in dataset):

    Sorry to say this but the page referenced in the explanation does not match the Microsoft page:

    SQL Server 2008 Books Online (November 2009)

    How to: Create a Dataset (Reporting Services)

    at:

    http://technet.microsoft.com/en-us/library/ms160345.aspx

    6. In Timeout, type the number of seconds that the report server waits for a response from the database. The default value is 0 seconds. When the time out value is 0 seconds, the query does not time out.

    The above page does not correspond to the authors statement that 30 seconds is the default value......hmmmm

    Now:

    http://technet.microsoft.com/en-us/library/ms160345(SQL.90).aspx

    SQL Server 2005 Books Online (November 2008)

    How to: Create a Dataset (Report Designer)

    Updated: 14 April 2006

    It Says:

    6. In Timeout, type the number of seconds that the report server waits for a response from the database.

    The default value is 30 seconds. Timeout must contain a value greater than zero or be left empty.

    If it is empty, the query does not time out.

    Here we go again another big arguement/discussion on the quality of the QOD .... OH WELL

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • Iggy-SQL

    SSCarpal Tunnel

    Points: 4169

    Sorry, your explanation and answer is only valid for SQL 2000. SQL 2008 requires the time out value to be 0 for the query not to time out. Whilst I appreciate you taking time to create the QotD, next time please specify the SQL version to avoid confusion. Furthermore, I never knew SQL 2000 reporting is also referred to as SSRS, as far as I know (but I know I have limited knowledge), the term SSRS started in SQL 2005 onwards.

    Reference for SQL 2008: http://msdn.microsoft.com/en-us/library/ms160345.aspx


    Urbis, an urban transformation company

  • Ron McCullough

    SSC Guru

    Points: 63877

    Iggy-SQL

    Check out this link:

    SQL Server 2005 Books Online (November 2008)

    Reporting Services Enhancements

    http://technet.microsoft.com/en-us/library/ms170438(SQL.90).aspx

    This may clear up some of the confusion then again it may not

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • SQLRNNR

    SSC Guru

    Points: 281252

    d'oh

    I missed this question due to going with documentation stating that 0 is the value that should be set.

    Most people have missed it so far - and that is kind of interesting. The reason for that happening seems to be differences found in documentation.

    hmmm....

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • This was removed by the editor as SPAM

  • Kelsey Thornton

    SSCrazy

    Points: 2157

    Until I read the posts here I was going to write "Good Question".

    I had to search around a bit until I found the answer.

    Looking at the MS web page http://msdn.microsoft.com/en-us/library/ms160345(SQL.90).aspx (to which I navigated after doing a search on MSDN), I found the "correct" answer.

    I think I'll still say "Good Question" anyway 🙂

    Kelsey Thornton
    MBCS CITP

  • Andeavour

    SSCrazy

    Points: 2570

    Should have read the question better. The defining clue was in "(in dataset)".

    Once you start looking into controling the timeouts in the Dataset, then you find the answer quoted in the documentation.

    Another lesson in reading the question more carefully 🙂

  • ohack

    SSCrazy

    Points: 2043

    A somewhat ambiguous question again - as in even knowing the answer still left 2 answers as valid. If you leave the timeout box empty and click ok (SSRS 2008) it will have a zero in it when you reopen it - or you can just put a zero in there. Needless to say I was unlucky and got it "wrong".

  • anna.ellis@getronics.com

    Default port

    Points: 1465

    I have to agree with those who have asked for the version of SQL Server to be specifed in future. SQL 2008 clearly states a value of 0 as the "never time out" value; SQL 2000 and 2005 state a value of blank or greater than 0.

    It's surely not a surprise that the majority of those who answered this question assuming that the unstated version meant the question referred to the latest version of SQL Server?

  • free_mascot

    One Orange Chip

    Points: 27168

    Me too... went wrong and lost the point 🙁

    The term used in question is SSRS which is not used for the SQL Server 2000 and the reference is given for the version SQL Server 2000.

    It would be good to have specific version.

    ---------------------------------------------------
    "Thare are only 10 types of people in the world:
    Those who understand binary, and those who don't."

  • sjimmo

    SSChampion

    Points: 11139

    :exclamationmark: I have a definite problem with this QOD. WHICH VERSION? When the version is missing, I assume that the question is referencing the most current version and not the one that is on extended support. The link provided is for SS2000. I believe that if the question was answered correctly for either of these versions, then the points should be given and the question marked as correct. The QOD SHOULD include the version that the question is about. Not having the version CAN cause the wrong answer, and thus the arguments seen lately.

    Having "assumed" SS2008, I answered 0. For 2005 and 2000, the answer is leave it empty. (See below)

    SQL Server 2000

    Timeout

    Type the number of seconds until the query times out. The default is 30 seconds. The value for Timeout must be empty or greater than zero. If it is empty, the query does not time out.

    SQL Server 2005

    Timeout

    Type the number of seconds that the report server waits for a response from the database. The default value is 30 seconds. Timeout must contain a value greater than zero or be left empty. If it is empty, the query does not time out.

    SQL Server 2008

    Timeout

    In Timeout, type the number of seconds that the report server waits for a response from the database. The default value is 0 seconds. When the time out value is 0 seconds, the query does not time out.

    Steve Jimmo
    Sr DBA
    “If we ever forget that we are One Nation Under God, then we will be a Nation gone under." - Ronald Reagan

  • Steve Jones - SSC Editor

    SSC Guru

    Points: 720887

    The question has had the version added.

  • Chad Crawford

    SSChampion

    Points: 11610

    As Scooby would say, "Ruh rhow!" - there seems to be a conflict in the documentation. Timeout Element (SQL 2000) states:

    The value for the Timeout element must be between 0 and 2147483647. If the value is omitted or is 0, the query does not time out.

    Anyone have 2000 installed that can see what really happens?

    Thanks,

    Chad

  • Oleg Netchaev

    SSCertifiable

    Points: 5272

    As far as the SqlCommand is concerned, there is only one way to set the timeout such that report does not time out - set it to zero. In other words, even though documentation for SQL Server 2005 states to leave it blank, what happens under the hood is that CommandTimeout property, which "gets or sets the wait time in seconds before terminating the attempt to execute a command and generating an error", ends up with the value equal to zero. It has always been like this, even in old ADODB. Too bad that Microsoft changed the usual way of instructing queries not to timeout from the traditional set it to zero to leave it blank in SQL Server 2000/2005 (which will under the hood set it to zero for you).

    With version added, this happens to be a very good question. I missed it because CommandTimeout = 0 seems to be the only way to do it correctly. As a matter of fact, if you use the code to programmatically set the CommandTimeout then there is no GUI to do it for you and you do indeed have to type [yourCommandInstance].CommandTimeout = 0, because in the code it will not accept the value of blank and if you don't explicitly set it then it will get its respective default value, which happens to be 30 seconds. 🙂 This is still true in any version.

    Oleg

Viewing 15 posts - 1 through 15 (of 26 total)

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