then, and as I said on the options, hardcode the path to the SQL Server BCP and do it that way.

easy and fast - just not portable to other servers...

Sorry but this solution is not professional in all terms. Components exist within a server for some reason, and the solution is not always to remove them in order...

basic solutions that any professional should be able to figure out after the issue has been found.

• remove whatever sybase components you have on the server
• change path order
• hardcode...

ohhh.. it does look like I was right after all.

• This reply was modified 4 years, 7 months ago by frederico_fonseca.

what error?

in SQL Server BCP the command works fine and outputs the version of BCP - on other versions of BCP (such as yours) it may error but without its...

• This reply was modified 4 years, 7 months ago by frederico_fonseca.

as you didn't read what I said, neither the link, please...

hum. based on the output you gave us you are executing a Sybase BCP command - so either you not using SQL Server or the server you are executing the...

• This reply was modified 4 years, 7 months ago by frederico_fonseca.

can you post the code here - without it we can't tell you what you are doing wrong - but normally its a small thing like missing quotes somewhere.

possibly because it is a cluster and it has its own IP - which will be different from the local host (cluster node)

@Sergiy - for sake of consistency can you give your version (condensed) that gives both outputs I gave - and taking in consideration that either today or yesterday could be...

modified version that solves that particular issue - previous one was really just addressing the parsing, not the accuracy of the output.

this version also addresses possibility of more than 99...

this will work as long as difference does not go past 31 days

SELECt RIGHT(CONVERT(varchar(19) -- always put the size when defining datatype - do not use defaults...

although going through the route of linked server best practices would mean that the linked server would not be named as the server name but rather as a logical name...

ahhhh... and issue is that its not only SQL developers that introduce "issues" like this.

A EF extension (https://github.com/borisdj/EFCore.BulkExtensions) built to make it easier for C# developers to do high speed...

although. 2 ms for a dynamic sql? how often is this executed during the day? unless it is being executed hundreds of times per minute I would not bother too...