You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a single script for a stored procedure or function, obtained by SchemaZen, perform on the database by the utility sqlcmd -i (after removing the existing object from the database), and then again get it via SchemaZen, the new version of the script will be different from the old version one empty line, although no manual modifications to the script file was not fulfilled.
It seems the new line is added to the definition of the object after it is created from a script by sqlcmd -i. Because the line with the following GO written to the definition as a carriage return.
The text was updated successfully, but these errors were encountered:
AlexeyKasjanov
changed the title
When generating a script for the object of stored procedure or function, one extra empty line is added to the end of script.
When generating a script for the object of stored procedure or function, one extra empty line is added to the end of definition.
Nov 3, 2015
I've also noticed similar issues with extra new lines being add to the beginning and end of scripts. Perhaps you could parse it to remove all newlines between the "GO" & the first proc line, and the last proc statement & the following "GO" statement.
If a single script for a stored procedure or function, obtained by SchemaZen, perform on the database by the utility sqlcmd -i (after removing the existing object from the database), and then again get it via SchemaZen, the new version of the script will be different from the old version one empty line, although no manual modifications to the script file was not fulfilled.
It seems the new line is added to the definition of the object after it is created from a script by sqlcmd -i. Because the line with the following GO written to the definition as a carriage return.
The text was updated successfully, but these errors were encountered: