[dba-SQLServer] SPAM-LOW: SQL Server name does not match @@Server

Hey, I am slowly getting better at this stuff.  That was indeed the problem.  As soon as I renamed 
the sql server instance using code I found on Google the BCP stuff worked.

Yea!

John W. Colby
www.ColbyConsulting.com


jwcolby wrote:
> My SQL Server instance APPEARS to be named Stonehenge, the machine is named Stonehenge, but 
> @@ServerName returns Colby-1393B53EE.  AFAICR in the previous install it was named Stonehenge.
> 
> Is this going to cause me a problem?
> 
> I am trying to execute code:
> 
> bcp "SELECT * FROM dbo.DataDepot_vPSMOrderAccuzipOut" queryout 
> E:\PSM\Data\DataDepot\AccuzipInputTo\DataDepot_0MTo1000M.txt -c -t, -T -S COLBY-1393B53EE (@@ServerName)
> 
> and getting an error:
> 
> SQLState = 08001, NativeError = 53
> Error = [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL 
> Server [53].
> SQLState = 08001, NativeError = 53
> Error = [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the 
> server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the 
> default settings SQL Server does not allow remote connecti
> ons.
> SQLState = S1T00, NativeError = 0
> Error = [Microsoft][SQL Native Client]Login timeout expired
> NULL
> 
> If I had to guess (which I have to do) I would say the @@Server is not returning what the BCP 
> expects to see.
>