Francisco Tapia
fhtapia at gmail.com
Tue Jun 2 09:40:33 CDT 2009
Did you rename your host machine? It looks like it because otherwise the @@ServerName is the same as the host name of the computer. In Sql Server 2000 and 7.0 iirc, you had to drop and re-add the server name like so: sp_dropserver 'old server name' sp_addserver 'new server name' , 'local' -Francisco http://sqlthis.blogspot.com | Tsql and More... On Mon, Jun 1, 2009 at 6:18 PM, jwcolby <jwcolby at colbyconsulting.com> 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. > > -- > John W. Colby > www.ColbyConsulting.com > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > >