I have an app that has some stored procedures running queries across a linked server. In our development environment, the linked database is on a box called 10.xxx.xxx.xx. In the production environment, the linked database will be on a server called something else. What I want to do is have the linked server in the development environment named the same thing as the linked server in the production environment, so that I won't have to change the stored procedures when migrating the project into production.
SQL Server 2005 isn't giving me the option to rename or alias the linked server, though. Is there anyway to do this so that I can have the linked server named the same thing on the two different boxes and not have to change the sp's?
Hi , On my Desktop i registered Production Server in Enterprise Manager on that Server if i go to SecurityLinked Servers There is another Server is already mapped, when i am trying to see the Tables under that one of the Linked Server i am getting the Error message saying that "Error 17 SQL Server does not exist or access denied"
if i went to Production Server location and if i try to see the tables i am able to see properly, no problems why i am not able to see from my Desk top i am using the sa user while mapping the Production Server on my DESKTOP using (ENTERPRISE MANAGER)
And i check the Client Network Utility in the Alias using Named Pipe only, i changed to TCP/IP still same problem What might the Problem how can i see the Tables in Linked Server from my DESKTOP
Can anybody please tell me how to rename an sql server express. I have an SQL server instance named 'PC075/Sqlexpress'. I have to change it to 'PC075'. Thanks,
if my computer name is x and sql server was installed and therefore took on the default name of x, can I change the sql server name to y at a later date while the computer name remains as x? If so how do I do it?
The sp_addserver is internal recognition. But I want to connect to sql server using the new name y. I am assuming setup needs to be run only if computer name also changes to y and this is not the case.
I would like to rename my SQL server. Someone suggested SQLServer and we went with it, but after some discussions with other developers we thought that this name would be a hackers delight. So now I need to rename it to something that wouldn't put a "bulls eye" on its back. Any suggestions? :-)
This machine is not in production just yet, so if I had to reinstall SQL it wouldnt' be that bad of an option.
Hello, I want to rename a server NT4 on whom is bases sql server sql 7 sp 2, who is the precautions to set and can you indicate me the procedure. Thank you in advance. pascal
I inherited a sql server that I have always known as cmsphdb5 setup by a former dba. newer Junior dba tries to install LiteSpeed and he gets and error about server name mismatch. I go to QA and run select @@servername and I get cmdphdb5. Can I sp_dropserver cmdphdb5 and then sp_addserver cmsphdb5?
I have an SQL Server 2000. I need to rename the box that it is installed on and then rename the SQL Server to have the same name as the what the server was renamed to. How do I go about this? What are the steps? Thanx
I am using SQL Server 2005 in a test environment and I want to rename the server to match my production environment. Currently the name is the same as my computer name. Can it be changed? Do I have to change my computer name? (My computer is not on the same network so it is possible).
Hi, I was looking to a server which was renamed from A_old to A_new. but the problem is the system table still shows an entry with A_old and is taking this as a local server name. Any ideas how to do this?Do I have to stop the services for this?run setup again?and then sp_dropserver and sp_addserver is the answer to this?or there is any other solution to it? Note:this is a productionBox. Any thoughts appreciated?
I have change the name of my host by "network neighborhood" and user sp_dropserver and sp_addserver. But when rebooting the host, I have this following message.
"Your SQL Server installation is either corrupt or has been tampered with (unknown package id). Please run setup."
But I change the name of the hostanme to the former name, there is no error.
We have an NT 4.0 member server in a production domain which has SQL 6.5 loaded with a number of databases. There is a requirement to rename the NT server to another name. Will we have to reinstall SQL and reload any databases after the server is renamed? If not - are there any other considerations/registry changes necessary to ensure SQL will run correctly?
I am installing SQL Server 2005 on a couple of servers where the windows server will later be renamed. One is a default instance, and one is a named instance.
Does anyone have a procedure for this, or know any gotchas for 2005? I have done this for SQL 2000 many times, but never of 2005.
Books Online seems to say you just rename the server, and everything will be OK.
I know how to rename the server internally with sp_dropserver and sp_dropserver. It looks like you no longer have to update originating_server in msdb.dbo.sysjobs, because it was replaced by originating_server_id.
We have a new SQL Server 2005 box in place and we named this server - Server2. Restored all the production databases from original Server1. Server1 is running SQL Server 2000 Enterprise Edition. Server1 also has three subscribers ServerA, ServerB, and ServerC.
After Server2 was renamed to Server1 and Server1 decommissioned, replication is not working on the new Server1 due to the renaming issue. I can afford to re do replication from ground up on Server1 but cannot reinstall SQL Server 2005 and start from scratch since the server is already in production.
How can I resolve this issue? What is the right approach to take for the scenario described above?
I'm trying to write a script to run after changing the computer name of a machine running SQL Server 2005. I know about the article on the SQL Developer center that talks about sp_dropserver and sp_addserver. My question is about the Windows groups that are created with the machine name embedded inside (e.g. MACHINENAMESQLServer2005MSFTEUser$MACHINENAME$MSSQLSERVER).
Do I need to worry about these? If the answer is no because the name of the group is irrelevant, how do I go about changing the machine name for the login (i.e. the MACHINENAME in front of the slash)? I don't want to hardcode these group names into my script.
Do I have to do anything when hostname (servername) with SQL Server 2005 install was changed from OLDNAME to NEWNAME? If yes, what need to be done and syntax? I notice it under SYSSERVERS table still contain the OLDNAME.
How does one make a copy of a database (with the data) on the sameserver. Would like to do this to use the copy in a test environment. Ilooked at the Copy Database Wizard but the instructions in Books Onlinestate that the database must be copied to another server and cannot berenamed using this process.Thank you.
Sorry 'bout my bad english. Is there any possibility, to change the current server name from the stuctureview in the Enterprise Manger. I'm registering a lot of online-servers from my customers. The remote servername is fixed of course, but I want to change it local, to explain it a little bit better (e.g. "W2KSQLSRV" -> "CustomerXY")
Scenario 1: Windows 2000 Server SQL Server 2000 with default name installation. When we change the Windows Server name the SQL Server jobs becomes non editable.
Scenario 2: Does this situation still exists for the following configuration? Windows Server 2003 SQL Server 2005.
Question 1: I am planning to move the SQL Server from 2000 to 2005 as described in scenario 1 to scenario 2. Does changing the server name have any impact on previously created jobs? Does the jobs becomes non editable.
Question 2: Is it possible to have two servers with same name on a network? If possible, please elaborate. Thank you, Smith
I want to Replace The Big Log database with A new one ( A database with same structure).But current DB has many connection .
This is my plan :
1- Create a new database with same structure.
2- Rename current database to olddb with this code :
USE master GO EXEC sp_dboption CurDataBase, 'Single User', True EXEC sp_renamedb 'CurDataBase', 'OldDataBase' GO 3- Rename Newdb to current DB. USE master GO EXEC sp_renamedb 'NewDataBase', 'CurDataBase'
is it true ? and Tsql code is ok ? (dont forget many of connection to curdatabase (that Is a log db) and loss some seconds data is not problems)
I installed sql server on one of my test servers, and I am eventually going to rename this server and put it into production. This server will replace one of my old servers with the same name. I was wondering if there was a way to rename the SQL Server instance after you rename your server without having to reinstall SQL Server. Thanks in advance for all the help.
If you drop / rename a table and then recreate the table with the SAME NAME, what impact does it have on stored procedures that use these tables? From a system perspective, do you have to rebuild / recompile ALL the stored procedures that use this table?
I had a discussion with someone that said that this is a good idea, since the IDs of the tables change in sysobjects and from a SQL SERVER query plan perspective, this needs to be done...
Question 2
If you Truncate a Table as part of a BEGIN TRANSACTION, what happens if an error occurs? Will it Rollback? The theory is that it won't because Truncate doesn't utilize the logs where as Delete From uses the SQL Logs?
