print & nvarchar(max)/varchar(max) - by Bryan Aldrich

Status : 

  Postponed<br /><br />
		Due to current priorities, the product team decided to postpone the resolution of this item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


40
0
Sign in
to vote
ID 196643 Comments
Status Closed Workarounds
Type Bug Repros 18
Opened 9/6/2006 10:16:52 PM
Access Restriction Public

Description

when using nvarchar/varchar parameters with the (max) option, any print statement crops the output.
Sign in to post a comment.
Posted by Stoica Andrei on 7/7/2014 at 7:05 AM
This isn't fixed in 2008 R2, what is happening?
Posted by Michael_S√łndergaard on 12/5/2009 at 4:30 PM
This issue is especially annoying, when you are creating utility stored procedures, which generates large transact code output. Now we have to print code in small piece and this can actually break the script, because the outputtet code, could be split in the middle of a keyword
Posted by TomThomson on 10/26/2009 at 5:34 AM
We see far too many half-baked features, and they are all very irritating and require us to write a lot of code that ought to be unneccessary. This is a classic example of that sort of mistake by MS.
Posted by LGibson69 on 7/29/2009 at 11:53 AM
I agree, this is just lazy coding on Microsoft's part. Why put in a feature if it's not fully functional? Do they enjoy just teasing us or something? Come on Microsoft, I would get canned if I did something like this.
Posted by _Aleks on 7/29/2009 at 5:51 AM
I can't understand why MS does something in half. Make it in full or just don't do it!
Posted by way0utwest on 7/10/2009 at 10:50 AM
If you can store it, the tools should be able to access it. This can be a setting in SSMS to set the max display, but it should be the limit of storage if someone needs that.
Posted by Microsoft on 9/26/2006 at 2:21 PM
Thank you for bringing this issue to our attention. This issue is not sufficiently critical to fix in SP2. However, we will consider fixing this in a future release of SQL Server.

Regards,
Tomer
SQL Server Development