Lynn Pettis (9/20/2012)

---

YSLGuru (9/20/2012)

---

Lynn Pettis (9/19/2012)

---

Bump. Have you tried my latest change? You know, not including the [ ] around the server name and instance name with the -S parameter to bcp?

Lynn,

I'm just now getting back to working on this. I just tried your last suggestion and that one DID work. While I'm gald to get this working I am curious as to what it is about the new server that reuires this kind of change. Is it just because its a named instance?

Yes, as I believe I mentioned a few posts back. When you don't include the -S parameter BCP attempts to connect to the default instance of SQL Server on the server that it is being run on. This is why it would run on the old server. You were probably able to access the data on the new server, and this is a guess on my part, because you probably have a linked server defined on the old server pointing to the new server. When you added the -S parameter, the problem then was we kept the square brackets around the servername\instancename and bcp didn't like it. That's when I played with bcp on my laptop and found that those needed to go bye bye.