We moved Navision to a named instance of a big 64 bit SQL Cluster. After we got the SQL 64 win-authentification procedure everything works fine. Today i realized that im no longer able to rename fields in table on this database. I got an error message like: SQL… the qualified @oldname references to a database (“correct name of the database”) other than the current database. I suppose a procedure responsible for saving changes of navision objects fails by handling the 64 bit SQL, cluster names. The named instance must have a “” in the servername. This could be the reason. Is there any reported bug or better patch to solve this problem? Maybe it’s not a 64bit problem, but on our test-database on the same server i got this error too. Restoring a backup on a lokal PC i got no Problems at all. Version of Navision = 3.70a Version of Database = 2.xx Server W2000 / Itanum SQL2000 / Itanum Any help is welcome 
Bye(Stefan); Subject changed because of clarification
Update: From the Server / SQL-Administrator i will get the possiblility to test our database on the default instance to find out if the problem is caused by named instances. Outcome will be posted asap. Bye(Stefan);
Now i’m shure…it’s a problem running navision on the “named instance” (perhabs it don’t matter if SQL32 or SQL64). The test descibed above cannot reproduce the failure. So are there any expiriences running Navision on a named instance? Im 99% shure the problem is caused by the Backslash in the servername (named instances affort this[:(]). Is this a known problem? Please help!!
I thougth i have a workaround using an alias Connection to the named instance but unforunatly Navision replaces this Alias with the real name of the sql instance. By testing this workaround i found out, that i got this problem only working on the terminal server. Switching over to my local client, i can reanme rename fields with any problems. Bye(Stefan);
My development environment is upon a named instance of SQL and i can not recall having this issue ever. Will check this out but i’m sure i have renamed fields before on this environment.
Sounds like a specific issue with 64-bit SQL only; named instances are generally not a problem and the error you are reporting (the use of sp_rename to rename an object) does not even include a server name. The error used to be caused by bad characters in column names, which confuses sp_rename, but that shouldn’t be an issue any more. If removing the named instance solves it, then it must be the problem (unless something else has also changed in your new test) - but I dont understand it.