Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 


 
     
Recent Posts
   
Popular Topics
Home   
Search
    Members    Calendar    Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by Stewart Campbell » String length?
Add to briefcase
29 posts, Page 1 of 3
123»»»

String length? Expand / Collapse
Rate Topic
Display Mode
Topic Options
Author
Message
Stewart "Arturius" Campbell
Posted Saturday, April 10, 2010 5:36 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 3,129, Visits: 4,312
Comments posted to this topic are about the item String length?

____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
Post #901160
Paul White
Posted Sunday, April 11, 2010 4:05 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 5:10 PM
Points: 10,989, Visits: 10,535
Very clever question - with some well-thought-out wrong answers

First one to whinge about the explanation being 'incomplete' gets a banana

Well done.


Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #901211
Joy Smith San
Posted Sunday, April 11, 2010 10:54 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 8:35 PM
Points: 1,371, Visits: 2,301
haaaa..very good question.. fortunately I got it right.
Wel, I would like to know...

1. When a query will timeout.?
2. When execution of something will run out of memory.?

thanks.
Post #901342
Hugo Kornelis
Posted Monday, April 12, 2010 12:26 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:02 PM
Points: 5,243, Visits: 7,055
Joy Smith San (4/11/2010)
haaaa..very good question.. fortunately I got it right.
Wel, I would like to know...

1. When a query will timeout.?
2. When execution of something will run out of memory.?

thanks.


I can answer the first question. From the server's point of view, queries never timeout. Timeout is a client setting. A client that supports it will send a cancel signal to the server (causng the transaction to be aborted and rolled back) when the set maximum execution time has passed.

Hugo Kornelis, SQL Server MVP
Visit my SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
Post #901366
Christian Buettner-167247
Posted Monday, April 12, 2010 1:18 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 6:12 AM
Points: 2,526, Visits: 3,620
Paul White NZ (4/11/2010)
First one to whinge about the explanation being 'incomplete' gets a banana

Me want the banana *whingingabouttheexplanation*! :D

No results returned, as an infinite loop is invoked. But even if there was no infinite loop, no results would be returned, as the variable is not defined as OUTPUT.


But still, good question & explanation. More of that please!

Best Regards,
Chris Büttner
Post #901390
Bob Cullen-434885
Posted Monday, April 12, 2010 1:56 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: 2 days ago @ 8:52 AM
Points: 508, Visits: 388
I had the same initial thought - it cannot RETURN a varchar, as return values are always int. So, that rules out one wrong 'un !!
Post #901398
Paul White
Posted Monday, April 12, 2010 2:34 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 5:10 PM
Points: 10,989, Visits: 10,535
Christian Buettner-167247 (4/12/2010)
Paul White NZ (4/11/2010)
First one to whinge about the explanation being 'incomplete' gets a banana

Me want the banana *whingingabouttheexplanation*! :D

No results returned, as an infinite loop is invoked. But even if there was no infinite loop, no results would be returned, as the variable is not defined as OUTPUT.


But still, good question & explanation. More of that please!

Excellent, Christian!


Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi

  Post Attachments 
banana.jpg (338 views, 2.56 KB)
Post #901408
ziangij
Posted Monday, April 12, 2010 3:42 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Friday, May 17, 2013 2:53 AM
Points: 1,529, Visits: 359
thanks, was about to ask why am i not getting any output... luckily i saw the reply...

Christian Buettner-167247 (4/12/2010)
Paul White NZ (4/11/2010)
First one to whinge about the explanation being 'incomplete' gets a banana

Me want the banana *whingingabouttheexplanation*! :D

No results returned, as an infinite loop is invoked. But even if there was no infinite loop, no results would be returned, as the variable is not defined as OUTPUT.


But still, good question & explanation. More of that please!
Post #901437
sjeniferal
Posted Monday, April 12, 2010 4:38 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, September 30, 2011 12:12 AM
Points: 213, Visits: 42
So it will execute this forever? But obviously it won't execute forever, correct? Is there a time limit within SQL Server after which long running queries will be killed? How does that work? I mean some queries will take a long time to run and some others like the one in this example are faulty and will run forever....

So, in this case the app will get a SQLTimeout error? I guess my question is what is the sequence of events internally inside SQL Server and between SQL Server and (a .NET) app that finally result in a SQLTimeout error?
Post #901453
Hugo Kornelis
Posted Monday, April 12, 2010 4:52 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:02 PM
Points: 5,243, Visits: 7,055
sjeniferal (4/12/2010)
So it will execute this forever? But obviously it won't execute forever, correct? Is there a time limit within SQL Server after which long running queries will be killed? How does that work? I mean some queries will take a long time to run and some others like the one in this example are faulty and will run forever....

So, in this case the app will get a SQLTimeout error? I guess my question is what is the sequence of events internally inside SQL Server and between SQL Server and (a .NET) app that finally result in a SQLTimeout error?

Unless some client decides that the query has run long enough, it will continue forever. Or at least until the next server reboot.

If a client (or a human) decides that the query has run long enough, an "Attention" signal will be sent to the server or a DBA will kill the process. That will cause a rollback (which will be pretty fast in this case, since no modifications are made) and a message to be sent to the client.

Hugo Kornelis, SQL Server MVP
Visit my SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
Post #901461
« Prev Topic | Next Topic »

Add to briefcase
29 posts, Page 1 of 3
123»»»

Permissions Expand / Collapse

 
 
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.