September 25, 2009 at 12:27 am
Comments posted to this topic are about the item @@TEXTSIZE
September 25, 2009 at 4:29 am
I got 2147483647 as result when I used select @@TEXTSIZE
Strange....
September 25, 2009 at 6:21 am
If you haven't set that yourself, then this line from 2008 BOL will explain it:
"The SQL Server Native Client ODBC driver and SQL Server Native Client OLE DB Provider for SQL Server automatically set TEXTSIZE to 2147483647 when connecting."
From the link provided by VM, you can see that is the maximum value allowed (2^31-1 : The max an integer datatype can store).
Try using SET TEXTSIZE 0 to set it to it's default value.
cheers
Rob
--------
[font="Tahoma"]I love deadlines. I like the whooshing sound they make as they fly by. -Douglas Adams[/font]
September 25, 2009 at 6:37 am
Yep you are quite right,
after SET TEXTSIZE 0
I got 4096
Thanks
September 25, 2009 at 9:42 am
Select @@TEXTSIZE
in SQL Server 2000 SP4 - result is 64512
in SQL Server 2005 SP3 - result is 2147483647
So, which one is correct?
SQL DBA.
September 25, 2009 at 11:08 am
So because the SQL native client sets it to 2gb, the question is ambigous in my opinion. I was expecting to see a 2gb answer. Whoever does a set @@textsize to 0 ??
Dennis Parks
MCSE, MCDBA, MCSD, MCAD, MCTS
September 30, 2009 at 9:38 am
dennisparks I'm also beaten here but maybe default confused us even more.
October 3, 2009 at 4:53 am
Try the following code, the returned result would be 4096:
SET TEXTSIZE 0
SELECT @@TEXTSIZE
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply