Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jimf
Master Smack Fu Yak Hacker
2875 Posts |
 Posted - 2011-08-25 : 11:19:44
|
| So there I was hapleesly hacking away at SQL. Created a table, went to populate and got an "object does not exist" error. I opened up SSMS and my 1.2.3.4 server connection gave me the databases associated with the 1.2.3.4\2008 instance! Our network admin (we have no dba) said just use 1.2.3.4\ to connect. Although this does work, it solves nothing, and we have to go into all our Excel and Access apps and change connection strings.I noticed when I went to do an Import via SSMS, that the server name appeared as 1.2.3.4" /NmyDatabase. Any idea of what went wrong or how to even start tracking this down?Thanks,JimEveryday I learn something that somebody else already knew |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
jimf
Master Smack Fu Yak Hacker
2875 Posts |
Posted - 2011-08-25 : 13:03:44
|
| Thanks Tara,We have no client-side aliases that I know of. I've always used the IP address in all my connections. The database is still there; I didn't lose any information. It's just that the connection 1.2.3.4 all of a sudden started connecting to 1.2.3.4\2008. 1.2.3.4 Has SQL 2005 installed (1.2.3.4) and SQL 2008 (1.2.3.4\2008).JimEveryday I learn something that somebody else already knew |
 |
|
|
jimf
Master Smack Fu Yak Hacker
2875 Posts |
Posted - 2011-08-25 : 13:35:15
|
| Well. Apparently someone placed an alias for 1.2.3.4 and that's what caused the problem!Thanks Tara!JimEveryday I learn something that somebody else already knew |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
Database "disappeared"