May 20, 2021 at 2:24 pm
I'm using "$(ESCAPE_NONE(DATE))$(ESCAPE_NONE(TIME))" in a job step which, according to the documentation, is supposed to be the date in YYMMDD format and the time in HHMMSS format. However, the stored procedure I'm running (which has a VARCHAR parameter) is getting:
So basically it's treating the time as an integer and stripping the leading "0"s
How can I stop this happening?
May 20, 2021 at 2:41 pm
Not sure about stopping it, but looks easy enough to handle in the proc, based on the differing lengths of the incoming string.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
May 20, 2021 at 3:19 pm
Yeah I've already implemented a workaround in this case but wanted to know for future implementations where this might not be possible.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply