Rename virtual SQL Server in cluster

Can I rename my virtual cluster name that has SQL 2005 installed after I
build it for example if the virtual name is MASTER_New to MASTER?
thanks,
Yes, check the books online for details.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
<msnews.microsoft.com> wrote in message
news:%23qPaVW5VHHA.1120@.TK2MSFTNGP02.phx.gbl...
> Can I rename my virtual cluster name that has SQL 2005 installed after I
> build it for example if the virtual name is MASTER_New to MASTER?
> thanks,
>
|||You can rename the cluster network name resource, but not the instance name
(not without a lot of registry hacks).
http://msdn2.microsoft.com/en-us/library/ms178083.aspx
Sincerely,
Anthony Thomas

<msnews.microsoft.com> wrote in message
news:%23qPaVW5VHHA.1120@.TK2MSFTNGP02.phx.gbl...
> Can I rename my virtual cluster name that has SQL 2005 installed after I
> build it for example if the virtual name is MASTER_New to MASTER?
> thanks,
>

Rename virtual server

Hi,
Is this possible to rename the virtual server in a cluster environnement
? I use SQL2000 with win2003 server.No. There is no supported way to rename a virtual instance in SQL 2000.
The closest way is to detach the user databases, uninstall SQL, reinstall
SQL, and reattach the user databases. You still have to fix login and
maintenance information manually.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"TheOne" <TheOne@.discussions.microsoft.com> wrote in message
news:9E540053-4D88-45EF-9454-41A6A888FD42@.microsoft.com...
> Hi,
> Is this possible to rename the virtual server in a cluster
> environnement
> ? I use SQL2000 with win2003 server.

Rename virtual server

Hi,
Is this possible to rename the virtual server in a cluster environnement
? I use SQL2000 with win2003 server.
No. There is no supported way to rename a virtual instance in SQL 2000.
The closest way is to detach the user databases, uninstall SQL, reinstall
SQL, and reattach the user databases. You still have to fix login and
maintenance information manually.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"TheOne" <TheOne@.discussions.microsoft.com> wrote in message
news:9E540053-4D88-45EF-9454-41A6A888FD42@.microsoft.com...
> Hi,
> Is this possible to rename the virtual server in a cluster
> environnement
> ? I use SQL2000 with win2003 server.

Rename virtual server

Hi,
Is this possible to rename the virtual server in a cluster environnement
? I use SQL2000 with win2003 server.No. There is no supported way to rename a virtual instance in SQL 2000.
The closest way is to detach the user databases, uninstall SQL, reinstall
SQL, and reattach the user databases. You still have to fix login and
maintenance information manually.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"TheOne" <TheOne@.discussions.microsoft.com> wrote in message
news:9E540053-4D88-45EF-9454-41A6A888FD42@.microsoft.com...
> Hi,
> Is this possible to rename the virtual server in a cluster
> environnement
> ? I use SQL2000 with win2003 server.sql

Rename SQL Server Virtual name in 2003 Cluster

Is it possible to change the current SQL virtual host name in Windows 2003?
and How?
I tried it by right click on the SQL Network name resource -> properties ->
parameters -> change the name. Then search the registry and change it to a
new name and reboot the node. It works but is there an easy way and is what
I did a safe procedure.
Thanks
Ayad
You sure can, see http://support.microsoft.com/?id=307336 for details
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Ayad" <ashammout1@.hotmail.com> wrote in message
news:%239vieFHsEHA.760@.tk2msftngp13.phx.gbl...
> Is it possible to change the current SQL virtual host name in Windows
> 2003?
> and How?
> I tried it by right click on the SQL Network name resource ->
> properties ->
> parameters -> change the name. Then search the registry and change it to a
> new name and reboot the node. It works but is there an easy way and is
> what
> I did a safe procedure.
> Thanks
> Ayad
>
|||Thanks Rod. But I don't want to un-install and re-install SQL to change the
name.
Ayad
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:%23X1xRMIsEHA.2732@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> You sure can, see http://support.microsoft.com/?id=307336 for details
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "Ayad" <ashammout1@.hotmail.com> wrote in message
> news:%239vieFHsEHA.760@.tk2msftngp13.phx.gbl...
a
>
|||Ok, that's cool. You know you don't have to reinstall. It's right click
rename, then sp_dropserver old_virtualservername
go, sp_addserver new_virtualservername, local go, etc.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Ayad" <ashammout1@.hotmail.com> wrote in message
news:eEPiKeJsEHA.2904@.TK2MSFTNGP15.phx.gbl...
> Thanks Rod. But I don't want to un-install and re-install SQL to change
> the
> name.
> Ayad
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:%23X1xRMIsEHA.2732@.TK2MSFTNGP09.phx.gbl...
> a
>
|||Hi
Not much choice. Clustering is one of those technologies that you follow the
KB articles exactly otherwise the whole thing comes apart and you end up
re-installing everything.
Sorry.
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ayad" <ashammout1@.hotmail.com> wrote in message
news:eEPiKeJsEHA.2904@.TK2MSFTNGP15.phx.gbl...
> Thanks Rod. But I don't want to un-install and re-install SQL to change
the[vbcol=seagreen]
> name.
> Ayad
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:%23X1xRMIsEHA.2732@.TK2MSFTNGP09.phx.gbl...
to
> a
>
|||I agree with Mike. The ONLY SUPPORTED way to rename a virtual SQL name is to uninstall and reinstall as documented in Microsoft Knowledge Base article
INF: How to Change a Clustered SQL Server Network Name
http://support.microsoft.com/?kbid=307336
This article has the following important NOTE
"Cluster Administrator provides a method to rename cluster resources. To do this, right-click the resource in Cluster Administrator and click Rename. However, if you
rename the SQL Server Network Name resource, a variety of situations could occur, the most critical being that the SQL Server virtual server instance may no longer come
online. "
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way
to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Rename SQL Server 2005 Virtual Server

Hi everybody,
I'm having a big problem when I want to rename my Failover Clustered SQL
Server 2005 Virtual Server. I've followed the indications given in this
how-to: http://msdn2.microsoft.com/en-us/library/ms178083.aspx but when I
try to bring my SQL Server online (after changing the network name, of
course...) I get this error:
[sqsrvres] GetRegKeyAccessMask: Could not get registry access mask for
registry key Software\Microsoft\Microsoft SQL Server\MSSQL.3\Cluster (status
0))
If I return back to the Virtual Server's old name I can bring SQL Server
online allright...
I've found no information about this error. Can anybody help me?
Thanks in advance,
Petrus
Create the following regkey:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsof t SQL Server\MSSQL.3\Cluster]
"ClusterName"="<NewVirtualServerName>"
I had the same problem, and MSSQL.3 referred to Reporting Services. I'm guessing that since Reporting Services isn't cluster aware, the parameters aren't updated (or even created). But when SQL starts all its instances up, it gets confused that the parameter isn't there to change.
However, this still didn't have the desired result for me. The database engine and the OLAP services were MSSQL.4 and .5 respectively. The cooresponding Cluster keys as above continually renamed themselves back to the old name.
-Tom Kretzmer
EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com
|||Sorry to post an update so soon. Just update MSSQL.4 and .5 on both nodes of the cluster and restart resources. For some reason "select @.@.servername" still comes up as the old instance name, but everything else works as it should.
EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Rename Server - SQL 2005 RS

Windows 2003 R2, SQL 2005
I use Virtual Server images for my testing environments and so I need to be
able to take my master copy of an image and rename the server so that I can
put out on the network. When I do this, Reporting Services is unable to
connect to the database, which is no surprise really. I'm having trouble
finding info on how to fix this.
Anyone know what's involved with getting reporting services to work if you
rename the server?
--
thanks,
-JeffHave you tried using the Reporting Services Configuration Utility? This
tool lets' you point to the correct server.
--
Shaun Beane, MCT, MCDST, MCDBA
dbageek.blogspot.com
"Jefffff" <Jefffff@.discussions.microsoft.com> wrote in message
news:6E591CBD-F70B-4F50-B289-5EDF4BDB6D1B@.microsoft.com...
> Windows 2003 R2, SQL 2005
> I use Virtual Server images for my testing environments and so I need to
> be
> able to take my master copy of an image and rename the server so that I
> can
> put out on the network. When I do this, Reporting Services is unable to
> connect to the database, which is no surprise really. I'm having trouble
> finding info on how to fix this.
> Anyone know what's involved with getting reporting services to work if you
> rename the server?
> --
> thanks,
> -Jeff|||Many moons later, I've found some time to test this...
What I find is that after renaming the server, the Configuration Utility
doesn't work. When you launch it, you need to first connect to an instance
of Reporting Services, before you can configure anything, and after renaming
the server, you cannot connect to the Reporting Services instance on that
server, therefore you cannot configure anything.
Unless I'm missing something, it seems renaming your server means
reinstalling SRS.
I'm not sure how the utility connects to an SRS instance. If I had the time
to figure that out, maybe I could figure out a fix.
Anyone else out there dealing with this one?
--
thanks,
-Jeff
"Shaun Beane" wrote:
> Have you tried using the Reporting Services Configuration Utility? This
> tool lets' you point to the correct server.
> --
> Shaun Beane, MCT, MCDST, MCDBA
> dbageek.blogspot.com
> "Jefffff" <Jefffff@.discussions.microsoft.com> wrote in message
> news:6E591CBD-F70B-4F50-B289-5EDF4BDB6D1B@.microsoft.com...
> > Windows 2003 R2, SQL 2005
> >
> > I use Virtual Server images for my testing environments and so I need to
> > be
> > able to take my master copy of an image and rename the server so that I
> > can
> > put out on the network. When I do this, Reporting Services is unable to
> > connect to the database, which is no surprise really. I'm having trouble
> > finding info on how to fix this.
> >
> > Anyone know what's involved with getting reporting services to work if you
> > rename the server?
> >
> > --
> > thanks,
> > -Jeff
>
>

Rename Cluster Instance - New Hardware - Keep Name

Hello all,
We are moving a sql cluster to new hardware but would like to keep the same
server/virtual instance name.
Could anyone offer some advice on how to go about this or point us in the
direction of some Microsoft how to articles?
Many thanks, Simon
One method that may work is backing up the DBs from the existing instance,
taking the old instance down. Bringing up the new instance on the new cluster
hardware and performing a restore. You may also be able to backup the DBs
onto a volume on the new hardware (over the wire) and then perform a restore
on the new hardware using the .BAK files from the volume on the new hardware.
"Simon" wrote:

> Hello all,
> We are moving a sql cluster to new hardware but would like to keep the same
> server/virtual instance name.
> Could anyone offer some advice on how to go about this or point us in the
> direction of some Microsoft how to articles?
> Many thanks, Simon
>
>
|||Windows clustering depends on unique names within a domain. Keeping an
existing name is almost impossible. You can use DNS to redirect the old
instance name to the new name. When I move servers I generally use a manual
log shipping process to bring the new server "close" to the old one. I then
stop connections to the old server, finalize the logs, apply them to the new
server, then bring the new one up. If you only have a few client machines,
you can set local aliases to redirect connections. Otherwise, DNS is your
friend. Look up the SVC record type for DNS. It allows you to map a name
to an IP address and a specific port.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Simon" <reply@.togroup.com> wrote in message
news:%23$37STSHGHA.1424@.TK2MSFTNGP12.phx.gbl...
> Hello all,
> We are moving a sql cluster to new hardware but would like to keep the
> same server/virtual instance name.
> Could anyone offer some advice on how to go about this or point us in the
> direction of some Microsoft how to articles?
> Many thanks, Simon
>

Rename Cluster Instance - New Hardware - Keep Name

Hello all,
We are moving a sql cluster to new hardware but would like to keep the same
server/virtual instance name.
Could anyone offer some advice on how to go about this or point us in the
direction of some Microsoft how to articles?
Many thanks, SimonOne method that may work is backing up the DBs from the existing instance,
taking the old instance down. Bringing up the new instance on the new cluster
hardware and performing a restore. You may also be able to backup the DBs
onto a volume on the new hardware (over the wire) and then perform a restore
on the new hardware using the .BAK files from the volume on the new hardware.
"Simon" wrote:
> Hello all,
> We are moving a sql cluster to new hardware but would like to keep the same
> server/virtual instance name.
> Could anyone offer some advice on how to go about this or point us in the
> direction of some Microsoft how to articles?
> Many thanks, Simon
>
>|||Windows clustering depends on unique names within a domain. Keeping an
existing name is almost impossible. You can use DNS to redirect the old
instance name to the new name. When I move servers I generally use a manual
log shipping process to bring the new server "close" to the old one. I then
stop connections to the old server, finalize the logs, apply them to the new
server, then bring the new one up. If you only have a few client machines,
you can set local aliases to redirect connections. Otherwise, DNS is your
friend. Look up the SVC record type for DNS. It allows you to map a name
to an IP address and a specific port.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Simon" <reply@.togroup.com> wrote in message
news:%23$37STSHGHA.1424@.TK2MSFTNGP12.phx.gbl...
> Hello all,
> We are moving a sql cluster to new hardware but would like to keep the
> same server/virtual instance name.
> Could anyone offer some advice on how to go about this or point us in the
> direction of some Microsoft how to articles?
> Many thanks, Simon
>

Rename Cluster Instance - New Hardware - Keep Name

Hello all,
We are moving a sql cluster to new hardware but would like to keep the same
server/virtual instance name.
Could anyone offer some advice on how to go about this or point us in the
direction of some Microsoft how to articles?
Many thanks, SimonOne method that may work is backing up the DBs from the existing instance,
taking the old instance down. Bringing up the new instance on the new cluste
r
hardware and performing a restore. You may also be able to backup the DBs
onto a volume on the new hardware (over the wire) and then perform a restore
on the new hardware using the .BAK files from the volume on the new hardware
.
"Simon" wrote:

> Hello all,
> We are moving a sql cluster to new hardware but would like to keep the sam
e
> server/virtual instance name.
> Could anyone offer some advice on how to go about this or point us in the
> direction of some Microsoft how to articles?
> Many thanks, Simon
>
>|||Windows clustering depends on unique names within a domain. Keeping an
existing name is almost impossible. You can use DNS to redirect the old
instance name to the new name. When I move servers I generally use a manual
log shipping process to bring the new server "close" to the old one. I then
stop connections to the old server, finalize the logs, apply them to the new
server, then bring the new one up. If you only have a few client machines,
you can set local aliases to redirect connections. Otherwise, DNS is your
friend. Look up the SVC record type for DNS. It allows you to map a name
to an IP address and a specific port.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Simon" <reply@.togroup.com> wrote in message
news:%23$37STSHGHA.1424@.TK2MSFTNGP12.phx.gbl...
> Hello all,
> We are moving a sql cluster to new hardware but would like to keep the
> same server/virtual instance name.
> Could anyone offer some advice on how to go about this or point us in the
> direction of some Microsoft how to articles?
> Many thanks, Simon
>

Rename a SQL Server 2000 virtual server (Workaround)

I have read from the MS SQL Server 2000 High Availability book by Allan Hirt
that Renaming a SQL Server 2000 virtual server is neither possible or
supported.
What is a workaround to this procedure if you would like to move your
present virtual server to a new server? The database is 300 GB in size and
you have only several hours downtime.
Thanks.
You can manually log ship your database to the new system. I am assuming
you have a way to change your client connections fairly rapidly and you
don't have a huge number of logins to redo. You can log ship the database
and keep it only a little bit behind. You lock out the users (change
passwords is good) and backup/restore the last log bits. Shut down the
source, change the connection info, apply the tail of the log to the new
server and you are off to the races. Ideally, this can be done in less than
a hour IF you plan and test carefully.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Joe K." <JoeK@.discussions.microsoft.com> wrote in message
news:223534F8-06D7-4691-A3BD-E03091AFC330@.microsoft.com...
> I have read from the MS SQL Server 2000 High Availability book by Allan
Hirt
> that Renaming a SQL Server 2000 virtual server is neither possible or
> supported.
> What is a workaround to this procedure if you would like to move your
> present virtual server to a new server? The database is 300 GB in size
and
> you have only several hours downtime.
> Thanks.
|||I can corroborate what Geoff said. I'd just like to add that, if you set up
your app servers to point to an IP address and not the virtual server name,
then you can just change the IP's of the virtual servers once you have
shipped the last log.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:u%23$o3FIwEHA.2600@.TK2MSFTNGP09.phx.gbl...
You can manually log ship your database to the new system. I am assuming
you have a way to change your client connections fairly rapidly and you
don't have a huge number of logins to redo. You can log ship the database
and keep it only a little bit behind. You lock out the users (change
passwords is good) and backup/restore the last log bits. Shut down the
source, change the connection info, apply the tail of the log to the new
server and you are off to the races. Ideally, this can be done in less than
a hour IF you plan and test carefully.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Joe K." <JoeK@.discussions.microsoft.com> wrote in message
news:223534F8-06D7-4691-A3BD-E03091AFC330@.microsoft.com...
> I have read from the MS SQL Server 2000 High Availability book by Allan
Hirt
> that Renaming a SQL Server 2000 virtual server is neither possible or
> supported.
> What is a workaround to this procedure if you would like to move your
> present virtual server to a new server? The database is 300 GB in size
and
> you have only several hours downtime.
> Thanks.
|||Tom Moreau wrote:
> I can corroborate what Geoff said. I'd just like to add that, if you
> set up your app servers to point to an IP address and not the virtual
> server name, then you can just change the IP's of the virtual servers
> once you have shipped the last log.
I used to use a DNS alias instead of use the real name or ip address. Using
an alias it's possible to remap the pointer in DNS to the new server, flush
the dns cache, and the new server became operational for client access.
I use this method creating a DNS alias for every database. In this way I
have the possibility to move one (or more) database from one server to
another without change the connection string...

> Tom
Bye
Luca Bianchi
Microsoft MVP - SQL Server
http://mvp.support.microsoft.com
http://italy.mvps.org
|||Hey, that's cool!
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Luca Bianchi" <rightjoinREMOVE_THIS@.hotmail.com> wrote in message
news:2urj9lF2csdb6U1@.uni-berlin.de...
Tom Moreau wrote:
> I can corroborate what Geoff said. I'd just like to add that, if you
> set up your app servers to point to an IP address and not the virtual
> server name, then you can just change the IP's of the virtual servers
> once you have shipped the last log.
I used to use a DNS alias instead of use the real name or ip address. Using
an alias it's possible to remap the pointer in DNS to the new server, flush
the dns cache, and the new server became operational for client access.
I use this method creating a DNS alias for every database. In this way I
have the possibility to move one (or more) database from one server to
another without change the connection string...

> Tom
Bye
Luca Bianchi
Microsoft MVP - SQL Server
http://mvp.support.microsoft.com
http://italy.mvps.org

Removing Nodes from a Virtual Server?

I've build a SQL 2000 SP3a cluster on top of an 8 node Windows 2003 cluster.
We've decided to split the cluster up into 2 individual clusters and as such
I'm attempting to remove some of the cluster nodes from the Virtual Server
Definiton (as per the "Adding or Removing a Cluster Node from the Vritual
Server Definition" of
http://www.microsoft.com/technet/pro...clus.mspx#EGAA)
Anyway, I begin the SQL install and get to the Computer Name dialog where I
choose the virtual server name. I click next and the install GUI just
disapears. I check and setupsql.exe is continues to show up as running in
Taskman for about 10 minutes then just finishes up.
Any thoughts?
Anyone have any thoughts on this?
"Chris B." wrote:

> I've build a SQL 2000 SP3a cluster on top of an 8 node Windows 2003 cluster.
> We've decided to split the cluster up into 2 individual clusters and as such
> I'm attempting to remove some of the cluster nodes from the Virtual Server
> Definiton (as per the "Adding or Removing a Cluster Node from the Vritual
> Server Definition" of
> http://www.microsoft.com/technet/pro...clus.mspx#EGAA)
> Anyway, I begin the SQL install and get to the Computer Name dialog where I
> choose the virtual server name. I click next and the install GUI just
> disapears. I check and setupsql.exe is continues to show up as running in
> Taskman for about 10 minutes then just finishes up.
> Any thoughts?
|||Hi
Only 4 Nodes are supported on a cluster by SQL Server 2000. It is a setup UI
limitation.
You need to remove the installation like you installed it, with command
line.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:981588B6-717B-45C2-BBBA-F5C30A2AE5F2@.microsoft.com...[vbcol=seagreen]
> Anyone have any thoughts on this?
> "Chris B." wrote:
|||Hmm, thanks for the quick reply.
I don't believe I installed from a command line, but those few weeks were
pretty crazy Can you point me in the general direction of documentation
on the command line syntax? I assume you're talking about using the
sqlrem.bat file?
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> Only 4 Nodes are supported on a cluster by SQL Server 2000. It is a setup UI
> limitation.
> You need to remove the installation like you installed it, with command
> line.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:981588B6-717B-45C2-BBBA-F5C30A2AE5F2@.microsoft.com...
>
>
|||I have not seen any. It was in a discussion with a developer from the SQL
Server Development Team.
PSS might be able to help.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:22265BEA-AD19-4C06-BFE6-146D419CCE10@.microsoft.com...[vbcol=seagreen]
> Hmm, thanks for the quick reply.
> I don't believe I installed from a command line, but those few weeks were
> pretty crazy Can you point me in the general direction of
> documentation
> on the command line syntax? I assume you're talking about using the
> sqlrem.bat file?
> "Mike Epprecht (SQL MVP)" wrote: