What format is it in now? YYYYMMDD? MM/DD/YYYY? etc

Also, why not use a DATE (or DATETIME) column to store dates? That's what they're for. Makes everything so much easier.

What command are you running from SSMS to perform a file copy?

Have you configured the job to run as you?

What errors do you get with a straight copy?

Yeah, just wing it. I'm sure everything will be OK 🙂

Can we assume that you have a QA/Test environment which is intended to be a close-to exact copy of Prod? If so, does the problem happen there too?

If not, I'd...

Excellent, thanks for posting back.

No I've not been able to repro the issue in a Sandbox (what I say at the start of OP); that's one of the reason why I hated asking this,...

• This reply was modified 5 years, 11 months ago by Phil Parkin.

Is there a column on tbl_serveravailability which is not wide enough to accept the data which is being inserted into it?

• This reply was modified 5 years, 11 months ago by Phil Parkin.

If you were to run EXEC dbo.NoRepro;, then you would get the errors above. If, however, you ran the SQL inside the SP, then it would succeed.

No errors for me:

You could use dynamic SQL.

Query sys.Sequences to get generate the ALTER SEQUENCE SQL statements & then EXEC that.

--Edit: Apologies: just noticed that John already suggested this

• This reply was modified 5 years, 11 months ago by Phil Parkin.

Tonight, I'll be in a theatre orchestra pit for the 5th time this week.  No need for...

whereabouts...

Thanks, Mike. I am also from the UK.

When I Googled 'chad', I ended up learning a lot about a country in Africa, but nothing about hole-punch waste! 🙂

Is 'chad' an American term? I have no idea what it means!

If you're not really interested in seeing whether a duplicate insert was attempted, consider adding IGNORE_DUP_KEY = ON to your target table definition.

Your code then becomes much simpler.