A number of questions have been posted in the past regarding the
problems encountered when renaming a computer that is running SQL or
MSDE. I too have had these problems but recent experience prompts me
to suspect that it is permissible to rename a computer that is running
XP Pro with MSDE2000 without any such problems.
Does anyone know of, or can anyone direct me to official Microsoft
information which details the restrictions on renaming a host computer
that is running SQL2000 in its various forms (Enterprise, Standard,
Personal Ed, MSDE)
Thanks
In my experience (and those of my customers) when you rename a computer and
reboot, SQL Server will reconfigure itself to the new machine name just
fine. Of course any scripts, DTS packages, or any other processes and
procedures that reference the old server name will need to be brought up to
date.
Jim
"David Vanstone" <dave.vanstone@.fujitsu.com.au> wrote in message
news:78d72c83.0404122023.225e5433@.posting.google.c om...
> A number of questions have been posted in the past regarding the
> problems encountered when renaming a computer that is running SQL or
> MSDE. I too have had these problems but recent experience prompts me
> to suspect that it is permissible to rename a computer that is running
> XP Pro with MSDE2000 without any such problems.
> Does anyone know of, or can anyone direct me to official Microsoft
> information which details the restrictions on renaming a host computer
> that is running SQL2000 in its various forms (Enterprise, Standard,
> Personal Ed, MSDE)
> Thanks
|||Thanks for the response Jim, but earlier versions of MSDE and SQL
often fail to work if the computer is renamed although that does not
seem to be the case recently and I have heard a rumor the MSDE2003
will not have this problem. I would like to know the offical Microsoft
position on the, but it is hard to come by.
Thanks again.
"J Young" <thorium48@.hotmail.com> wrote in message news:<O1wV5RRIEHA.3664@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
> In my experience (and those of my customers) when you rename a computer and
> reboot, SQL Server will reconfigure itself to the new machine name just
> fine. Of course any scripts, DTS packages, or any other processes and
> procedures that reference the old server name will need to be brought up to
> date.
> Jim
> "David Vanstone" <dave.vanstone@.fujitsu.com.au> wrote in message
> news:78d72c83.0404122023.225e5433@.posting.google.c om...
|||I've only seen problems with SQL Server 7 (ie and MSDE v1).
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"David Vanstone" <dave.vanstone@.fujitsu.com.au> wrote in message
news:78d72c83.0404132223.739b363e@.posting.google.c om...
> Thanks for the response Jim, but earlier versions of MSDE and SQL
> often fail to work if the computer is renamed although that does not
> seem to be the case recently and I have heard a rumor the MSDE2003
> will not have this problem. I would like to know the offical Microsoft
> position on the, but it is hard to come by.
> Thanks again.
> "J Young" <thorium48@.hotmail.com> wrote in message
news:<O1wV5RRIEHA.3664@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
and[vbcol=seagreen]
to[vbcol=seagreen]
|||Greg is correct. This problem is only present in SQL 7.0 and MSDE 1. In
these version of SQL Server there is no concept of an instance name and the
server name that you would address is always the name of the machine (except
in the case of a SQL7 cluster, which is another topic altogether).
Jim
"David Vanstone" <dave.vanstone@.fujitsu.com.au> wrote in message
news:78d72c83.0404132223.739b363e@.posting.google.c om...
> Thanks for the response Jim, but earlier versions of MSDE and SQL
> often fail to work if the computer is renamed although that does not
> seem to be the case recently and I have heard a rumor the MSDE2003
> will not have this problem. I would like to know the offical Microsoft
> position on the, but it is hard to come by.
> Thanks again.
> "J Young" <thorium48@.hotmail.com> wrote in message
news:<O1wV5RRIEHA.3664@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
and[vbcol=seagreen]
to[vbcol=seagreen]
Showing posts with label computer. Show all posts
Showing posts with label computer. Show all posts
Friday, March 30, 2012
Monday, March 26, 2012
Rename SQL Default instance in cluster
HI GROUP
I have my production sql server computer name "sql2k"
and of course the default sql instant name as "sql2k"
because they're running on same box aand stand alone
server.
I do have another active\active sql cluster in place
node1 name is sql1 node 2 name sql2 and virtual computer
name sqlcluster. My default sql instance name
is "sqlserver1"
and it running on Node1 with failed over using Node 2
My sql second instance name is "sql/server2" and it
running on Node 2 with failed over using Node1.
I would like to rename my "sqlserver1" sql instance name to
my production sql name is "sql2k, my plan is to uninstall
the sql default instant on node 1 and reinstall sql with
the my sql production name after shutdown my prodution sql
server. my question is do I need to rename the computer
virtual server name too or just sql instance name?
Do any one have any idea what will cause any problem to
rename sql instance in cluster and of course the cluster
will have diff ip address with sql production server
only the name will be transfer to my default cluster on
node 1. Please give me any opinion if you have with this
Thanks a lot
You can't rename a SQL Server instance in a cluster. The only way to
accomplish this is to uninstall SQL Server and reinstall it. There aren't
any issues to doing this that I'm aware of. Just keep the name under 13
chanracters.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||Thanks
But I would like to transfer production sql name to the
default sql cluster name is it possible?
I know I can not have 2 sql name in the same network
but what if I shutdown my production and during the
reinstall sql on defaukt cluster Can I use my production
sql name for it? I still not clear if sql name using any
dns or wins like computer name on network if that the case
then where do I need to look for do a clean up of that name
before using it for my cluster?
Thanks a lot
>--Original Message--
>You can't rename a SQL Server instance in a cluster. The
only way to
>accomplish this is to uninstall SQL Server and reinstall
it. There aren't
>any issues to doing this that I'm aware of. Just keep
the name under 13
>chanracters.
>--
>Mike
>Principal Mentor
>Solid Quality Learning
>"More than just Training"
>SQL Server MVP
>http://www.solidqualitylearning.com
>http://www.mssqlserver.com
>
>.
>
|||Yes, you can reuse that name as long as the original server is offline. The
names that you use for the machine, cluster, and SQL Server are DNS
resolvable.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
I have my production sql server computer name "sql2k"
and of course the default sql instant name as "sql2k"
because they're running on same box aand stand alone
server.
I do have another active\active sql cluster in place
node1 name is sql1 node 2 name sql2 and virtual computer
name sqlcluster. My default sql instance name
is "sqlserver1"
and it running on Node1 with failed over using Node 2
My sql second instance name is "sql/server2" and it
running on Node 2 with failed over using Node1.
I would like to rename my "sqlserver1" sql instance name to
my production sql name is "sql2k, my plan is to uninstall
the sql default instant on node 1 and reinstall sql with
the my sql production name after shutdown my prodution sql
server. my question is do I need to rename the computer
virtual server name too or just sql instance name?
Do any one have any idea what will cause any problem to
rename sql instance in cluster and of course the cluster
will have diff ip address with sql production server
only the name will be transfer to my default cluster on
node 1. Please give me any opinion if you have with this
Thanks a lot
You can't rename a SQL Server instance in a cluster. The only way to
accomplish this is to uninstall SQL Server and reinstall it. There aren't
any issues to doing this that I'm aware of. Just keep the name under 13
chanracters.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||Thanks
But I would like to transfer production sql name to the
default sql cluster name is it possible?
I know I can not have 2 sql name in the same network
but what if I shutdown my production and during the
reinstall sql on defaukt cluster Can I use my production
sql name for it? I still not clear if sql name using any
dns or wins like computer name on network if that the case
then where do I need to look for do a clean up of that name
before using it for my cluster?
Thanks a lot
>--Original Message--
>You can't rename a SQL Server instance in a cluster. The
only way to
>accomplish this is to uninstall SQL Server and reinstall
it. There aren't
>any issues to doing this that I'm aware of. Just keep
the name under 13
>chanracters.
>--
>Mike
>Principal Mentor
>Solid Quality Learning
>"More than just Training"
>SQL Server MVP
>http://www.solidqualitylearning.com
>http://www.mssqlserver.com
>
>.
>
|||Yes, you can reuse that name as long as the original server is offline. The
names that you use for the machine, cluster, and SQL Server are DNS
resolvable.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
Rename machine with SQL server
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. MACHINENAME\SQLServer2005MSFTEUser$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.
Thanks for any help.
There is no need to do anything with those local groups. They're created when you install/setup sqlserver. When you change the computer name, you would need to update sqlserver so that its servername matches up with the computername. See the following article for more detail.
http://msdn2.microsoft.com/en-us/library/ms143799(SQL.90).aspx
Tuesday, March 20, 2012
Rename a Computer that is running MS SQL Server 2005
Hi everyone,
Here's what we want to achieve:
We have a production computer hosting a default instance of MS SQL
Server 2005 (Let's use the name DBSVRA)
We have another computer that is currently has a default instance of
MS SQL Server 2005 (DBSVRB)
Because DBSVRB is much faster, efficient, etc..., we want to move all
the databases from DBSVRA to DBSVRB
Now, we don't want to adjust our connection strings from our
applications, we want to simply
rename DBSVRB to DBSVRA.
I checked the following article:
http://msdn2.microsoft.com/en-us/library/ms143799.aspx and all the
criterias under "Before you begin" section is met.
a) We don't have a failover cluster --> can happen in the future
b) We don't have replication set-up --> can happen in the future
c) We are not using reporting services --> can happen in the future
d) No data mirroring --> can happen in the future
Anyway, after all of this, I just find that this might have adverse
effects by simply renaming a computer. For one, we have just tested
this scenario and while the rename of the server was successful and I
was able to log to MGMT Studio using the new name successfully.
However, I have noticed that under Security->Logins, the
<INSTANCENAME>\SQLServer2005MSFTEUser$<INTSANCENAME>
$MSSQLSERVER,<INSTANCENAME>\SQLServer2005MSSQLUser$<INSTANCENAME>
$MSSQLSERVER, <INSTANCENAME>\SQLServer2005SQLAgentUser$<INSTANCENAME>
$MSSQLSERVER
still have the <INSTANCENAME> of the old server name. Is this an
issue?
I don't know...while it's doable, I just don't feel comfortable about
this. What are your thoughts?Did you get any responses to this? I have the same concerns!!!
"audrey.nsh@.gmail.com" wrote:
> Hi everyone,
> Here's what we want to achieve:
> We have a production computer hosting a default instance of MS SQL
> Server 2005 (Let's use the name DBSVRA)
> We have another computer that is currently has a default instance of
> MS SQL Server 2005 (DBSVRB)
> Because DBSVRB is much faster, efficient, etc..., we want to move all
> the databases from DBSVRA to DBSVRB
> Now, we don't want to adjust our connection strings from our
> applications, we want to simply
> rename DBSVRB to DBSVRA.
> I checked the following article:
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx and all the
> criterias under "Before you begin" section is met.
> a) We don't have a failover cluster --> can happen in the future
> b) We don't have replication set-up --> can happen in the future
> c) We are not using reporting services --> can happen in the future
> d) No data mirroring --> can happen in the future
>
> Anyway, after all of this, I just find that this might have adverse
> effects by simply renaming a computer. For one, we have just tested
> this scenario and while the rename of the server was successful and I
> was able to log to MGMT Studio using the new name successfully.
> However, I have noticed that under Security->Logins, the
> <INSTANCENAME>\SQLServer2005MSFTEUser$<INTSANCENAME>
> $MSSQLSERVER,<INSTANCENAME>\SQLServer2005MSSQLUser$<INSTANCENAME>
> $MSSQLSERVER, <INSTANCENAME>\SQLServer2005SQLAgentUser$<INSTANCENAME>
> $MSSQLSERVER
> still have the <INSTANCENAME> of the old server name. Is this an
> issue?
> I don't know...while it's doable, I just don't feel comfortable about
> this. What are your thoughts?
>
>
Here's what we want to achieve:
We have a production computer hosting a default instance of MS SQL
Server 2005 (Let's use the name DBSVRA)
We have another computer that is currently has a default instance of
MS SQL Server 2005 (DBSVRB)
Because DBSVRB is much faster, efficient, etc..., we want to move all
the databases from DBSVRA to DBSVRB
Now, we don't want to adjust our connection strings from our
applications, we want to simply
rename DBSVRB to DBSVRA.
I checked the following article:
http://msdn2.microsoft.com/en-us/library/ms143799.aspx and all the
criterias under "Before you begin" section is met.
a) We don't have a failover cluster --> can happen in the future
b) We don't have replication set-up --> can happen in the future
c) We are not using reporting services --> can happen in the future
d) No data mirroring --> can happen in the future
Anyway, after all of this, I just find that this might have adverse
effects by simply renaming a computer. For one, we have just tested
this scenario and while the rename of the server was successful and I
was able to log to MGMT Studio using the new name successfully.
However, I have noticed that under Security->Logins, the
<INSTANCENAME>\SQLServer2005MSFTEUser$<INTSANCENAME>
$MSSQLSERVER,<INSTANCENAME>\SQLServer2005MSSQLUser$<INSTANCENAME>
$MSSQLSERVER, <INSTANCENAME>\SQLServer2005SQLAgentUser$<INSTANCENAME>
$MSSQLSERVER
still have the <INSTANCENAME> of the old server name. Is this an
issue?
I don't know...while it's doable, I just don't feel comfortable about
this. What are your thoughts?Did you get any responses to this? I have the same concerns!!!
"audrey.nsh@.gmail.com" wrote:
> Hi everyone,
> Here's what we want to achieve:
> We have a production computer hosting a default instance of MS SQL
> Server 2005 (Let's use the name DBSVRA)
> We have another computer that is currently has a default instance of
> MS SQL Server 2005 (DBSVRB)
> Because DBSVRB is much faster, efficient, etc..., we want to move all
> the databases from DBSVRA to DBSVRB
> Now, we don't want to adjust our connection strings from our
> applications, we want to simply
> rename DBSVRB to DBSVRA.
> I checked the following article:
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx and all the
> criterias under "Before you begin" section is met.
> a) We don't have a failover cluster --> can happen in the future
> b) We don't have replication set-up --> can happen in the future
> c) We are not using reporting services --> can happen in the future
> d) No data mirroring --> can happen in the future
>
> Anyway, after all of this, I just find that this might have adverse
> effects by simply renaming a computer. For one, we have just tested
> this scenario and while the rename of the server was successful and I
> was able to log to MGMT Studio using the new name successfully.
> However, I have noticed that under Security->Logins, the
> <INSTANCENAME>\SQLServer2005MSFTEUser$<INTSANCENAME>
> $MSSQLSERVER,<INSTANCENAME>\SQLServer2005MSSQLUser$<INSTANCENAME>
> $MSSQLSERVER, <INSTANCENAME>\SQLServer2005SQLAgentUser$<INSTANCENAME>
> $MSSQLSERVER
> still have the <INSTANCENAME> of the old server name. Is this an
> issue?
> I don't know...while it's doable, I just don't feel comfortable about
> this. What are your thoughts?
>
>
Monday, March 12, 2012
Removing SQL Express instances
Using SQL Express, UNDER COMPUTER management, SQL Server Configuraqtion Manager, SQL Server 2005 Network configuration Ihave the following listed instances
CSOLUTION - not listed under services
MSSQLSERVER - Disabled
SQLEXPRESS - Diaabled
SQLTEST - Disabled
SQLEXPRESSDATA - used by VB05 program
Questions
a) how do I delete all the instancces I do not use. In MSDE, each instance could be removed via the add/remove programs, but I don't see how to remove it under express
b) since SQLEXPRESS is the default for an SQL Express installation, I would like for the VBB05 program to use that instance; how do I do that?
Any help would be appreciated.
Bob
a) When you go to Add/Remove Programs, select the SQL 2005 entry and click on Remove. This will pop up a box showing the instances you have on your machine. You can select one from here and continue with the uninstall to remove it.
b) When you create your DB connection in your VB app, you'll need to supply a DB name to connect to. Here, use <MACHINENAME>/SQLEXPRESS and it will connect to that instance. You'd do the same thing to connect to any other named instance.
Thanks,
Sam Lester (MSFT)
Removing SQL Express instances
Using SQL Express, UNDER COMPUTER management, SQL Server Configuraqtion Manager, SQL Server 2005 Network configuration Ihave the following listed instances
CSOLUTION - not listed under services
MSSQLSERVER - Disabled
SQLEXPRESS - Diaabled
SQLTEST - Disabled
SQLEXPRESSDATA - used by VB05 program
Questions
a) how do I delete all the instancces I do not use. In MSDE, each instance could be removed via the add/remove programs, but I don't see how to remove it under express
b) since SQLEXPRESS is the default for an SQL Express installation, I would like for the VBB05 program to use that instance; how do I do that?
Any help would be appreciated.
Bob
a) When you go to Add/Remove Programs, select the SQL 2005 entry and click on Remove. This will pop up a box showing the instances you have on your machine. You can select one from here and continue with the uninstall to remove it.
b) When you create your DB connection in your VB app, you'll need to supply a DB name to connect to. Here, use <MACHINENAME>/SQLEXPRESS and it will connect to that instance. You'd do the same thing to connect to any other named instance.
Thanks,
Sam Lester (MSFT)
Subscribe to:
Posts (Atom)