SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSRS timeout


SSRS timeout

Author
Message
free_mascot
free_mascot
SSCertifiable
SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)

Group: General Forum Members
Points: 7131 Visits: 2250
Me too... went wrong and lost the point Sad

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
sjimmo
SSCarpal Tunnel
SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)

Group: General Forum Members
Points: 4698 Visits: 2907
Exclamation Mark 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
Steve Jones
SSC Guru
SSC Guru (138K reputation)SSC Guru (138K reputation)SSC Guru (138K reputation)SSC Guru (138K reputation)SSC Guru (138K reputation)SSC Guru (138K reputation)SSC Guru (138K reputation)SSC Guru (138K reputation)

Group: Administrators
Points: 138911 Visits: 19406
The question has had the version added.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Chad Crawford
 Chad Crawford
SSCarpal Tunnel
SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)

Group: General Forum Members
Points: 4213 Visits: 18732
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
Oleg Netchaev
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2155 Visits: 1816
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
Chad Crawford
 Chad Crawford
SSCarpal Tunnel
SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)

Group: General Forum Members
Points: 4213 Visits: 18732
Ahhh.... that might explain what looked like a contradiction. Maybe it is the GUI that accepts blank/zero but the XML underneath is always zero. That would make sense. Thanks!

Chad
SQLRNNR
SQLRNNR
SSC Guru
SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)

Group: General Forum Members
Points: 63339 Visits: 18570
Chad Crawford (2/15/2010)
Ahhh.... that might explain what looked like a contradiction. Maybe it is the GUI that accepts blank/zero but the XML underneath is always zero. That would make sense. Thanks!

Chad


Then at the very least, there should have been two possible correct answers. Either of the two answers blank or 0 should have been viable.

(just spurning on the debate)



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

SanjayAttray
SanjayAttray
SSCertifiable
SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)

Group: General Forum Members
Points: 5581 Visits: 1619
What a fluke. I got right. I thought it should be 0 but SSC would not post a simple question with 2 points. Apart from 0 only leave it blank looked a logical answer. What ever.

Discussion was good than the question.

SQL DBA.
SQLRNNR
SQLRNNR
SSC Guru
SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)

Group: General Forum Members
Points: 63339 Visits: 18570
I find it interesting that the question has only been answered correctly 10% of the time. And 70% of the people missing the question all missed it selecting the same answer.

Thanks for the question at any rate. I will go back to the darkness now :-P



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

bitbucket-25253
bitbucket-25253
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14923 Visits: 25280
Jason

And Steve was off today on a ski trip ... but he did manage to add to the question "SQL Server 2000". but said nothing about awarding points to thos who answered correctly, but incorrectly to the original question.

Shall I cry

I want my point awarded

as I said before "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

Before posting a performance problem please read
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search