Timeline for sp_add_jobstep add more than 4000 Character in @command parameter

12 events

when toggle format	what		by	license	comment
Jun 8, 2017 at 18:33	vote	accept	SqlWorldWide
Jun 3, 2017 at 4:02	history	tweeted			twitter.com/StackDBAs/status/870853154342154240
May 31, 2017 at 23:18	answer	added	RDFozz		timeline score: 1
May 31, 2017 at 19:38	answer	added	SqlWorldWide		timeline score: 0
May 31, 2017 at 18:35	comment	added	SqlWorldWide		@GarethLyons I thought about that. So I started deleting some white space and linefeed from the top and I do see additional characters (same amount that I clean up at the top).
May 31, 2017 at 18:27	comment	added	Gareth Lyons		Yep, and just tried successfully on 16/16 too. Maybe a rogue apostrophe somewhere?
May 31, 2017 at 18:18	comment	added	SqlWorldWide		sql2016/ssms2016 are you passing it as a variable? `DECLARE @command1 NVARCHAR(MAX)` then ` @command=@command1` .
May 31, 2017 at 18:16	comment	added	Gareth Lyons		np, just tried it on SQL2014 / SSMS 2014, happily accepts & displays commands over 4000 characters. What versions are you on? Thanks
May 31, 2017 at 18:09	comment	added	SqlWorldWide		@GarethLyons Yes I see that, Not sure what I was thinking. Edited my question. thx.
May 31, 2017 at 18:08	history	edited	SqlWorldWide	CC BY-SA 3.0	added 43 characters in body
May 31, 2017 at 18:05	comment	added	Gareth Lyons		"@command" is nvarchar(max). Although if you need to go higher I'd be looking at moving the code into a stored proc/file, for readability if nothing else!
May 31, 2017 at 18:01	history	asked	SqlWorldWide	CC BY-SA 3.0