InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 17:32:43 GMT20http://www.sqlservercentral.com/Forums/Topic1071530-338-1.aspx[quote][b]riswana (11/1/2012)[/b][hr]Hi, I am having the same problem. My query string is greater than 8000 characters. I am using varchar(max). Can someone assist urgently with a result, please.[/quote]It's easy. Write a stored procedure and use BCP to call the stored procedure.Thu, 01 Nov 2012 07:40:15 GMTJeff Modenhttp://www.sqlservercentral.com/Forums/Topic1071530-338-1.aspx[quote][b]riswana (11/1/2012)[/b][hr]Hi, I am having the same problem. My query string is greater than 8000 characters. I am using varchar(max). Can someone assist urgently with a result, please.[/quote]On computers running Microsoft Windows XP or later, the maximum length of the string that you can use at the command prompt is 8191 characters.so you need to shorten up whatever is being passed as a query to your bcp.use the query string to insert the data into a view, and use bcp to select from the view instead.see this very similar post, where the Original poster needed to change his bcp query to select from a view(or global temp table):[b][url]http://www.sqlservercentral.com/Forums/FindPost1378950.aspx[/url][/b]Thu, 01 Nov 2012 07:32:16 GMTLowellhttp://www.sqlservercentral.com/Forums/Topic1071530-338-1.aspxMaybe switch to a Powershell script.Thu, 01 Nov 2012 07:25:50 GMTbrosspaxedihttp://www.sqlservercentral.com/Forums/Topic1071530-338-1.aspxHi, I am having the same problem. My query string is greater than 8000 characters. I am using varchar(max). Can someone assist urgently with a result, please.Thu, 01 Nov 2012 03:42:00 GMTriswanahttp://www.sqlservercentral.com/Forums/Topic1071530-338-1.aspxI experienced this error, I now make sure I make nvarchar types with 4000 rather than using the max function.Also just a note on BCP. Ensure it's always on one line, else it won't work, won't even print, very annoying!Mon, 10 Sep 2012 04:33:41 GMTNesukehttp://www.sqlservercentral.com/Forums/Topic1071530-338-1.aspxThank Odin for the internet -- and GSquared for this post! You just saved me a lot of time.Fri, 07 Sep 2012 08:47:14 GMThaleyahttp://www.sqlservercentral.com/Forums/Topic1071530-338-1.aspxYou're welcome.It's probably because they haven't rewritten xp_cmdshell since SQL 2000, and that didn't have the max option available.Wed, 02 Mar 2011 06:36:48 GMTGSquaredhttp://www.sqlservercentral.com/Forums/Topic1071530-338-1.aspxWell good grief, that was the problem! Kinda misleading error message! Thanks.Wed, 02 Mar 2011 06:23:48 GMTbrosspaxedihttp://www.sqlservercentral.com/Forums/Topic1071530-338-1.aspxYou can't use varchar(max) with xp_cmdshell. Found that out the hard way. Try a finite number (I usually just go with either 1000 or 8000).Tue, 01 Mar 2011 14:45:53 GMTGSquaredhttp://www.sqlservercentral.com/Forums/Topic1071530-338-1.aspxHere are the contents of @Cmd (varchar(max)):bcp "SELECT [Data] FROM myserver..dbo.PEC_Citrus_RptData where [Data] is not null order by [Data]" queryout "C:\Documents and Settings\All Users\Documents\Shared\OutputFile.txt" -c -t -T -S "MYMACHINE\MYINSTANCE"Here's the code: EXEC master..xp_cmdshell @Cmd ;Here is the error:Msg 214, Level 16, State 201, Procedure xp_cmdshell, Line 1Procedure expects parameter 'command_string' of type 'varchar'.?Tue, 01 Mar 2011 13:01:10 GMTbrosspaxedi