renaming drive letter

I want to add a new drive to replace an existing drive used by SQL
server(cluster installation).
My plan is to
1. stop sql related services.
2. copy sql db files to new drive...
3. Rename new drive with existing drive letter.
4. start sql.
My question is - will the change of drive letter work normally for cluster
installations or do i need to take any special care?If the drive letter is the same, the original files and directories are put
back, and the account running SQL Server has permissions to the files then
SQL won't detect any difference and be fine. However,
the cluster service may be a different story.
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DD1F651A-F5D2-49B0-A220-3BD6343E815D@.microsoft.com...
>I want to add a new drive to replace an existing drive used by SQL
> server(cluster installation).
> My plan is to
> 1. stop sql related services.
> 2. copy sql db files to new drive...
> 3. Rename new drive with existing drive letter.
> 4. start sql.
> My question is - will the change of drive letter work normally for cluster
> installations or do i need to take any special care?|||Hi
Changing a drive letter in a cluster becomes a lot more complicated as the
cluster services depend on it.
You have to between steps 2 and 3, remove the dependency in cluster manager,
then re-name the letter, establish the dependencies in cluster manager and
then start SQL Server.
It is best to take SQL Server and Agent offline, and then reboot each node
to make sure the groups and resources fail over correctly. Then bring SQL
Server online again.
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/
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DD1F651A-F5D2-49B0-A220-3BD6343E815D@.microsoft.com...
>I want to add a new drive to replace an existing drive used by SQL
> server(cluster installation).
> My plan is to
> 1. stop sql related services.
> 2. copy sql db files to new drive...
> 3. Rename new drive with existing drive letter.
> 4. start sql.
> My question is - will the change of drive letter work normally for cluster
> installations or do i need to take any special care?

renaming drive letter

I want to add a new drive to replace an existing drive used by SQL
server(cluster installation).
My plan is to
1. stop sql related services.
2. copy sql db files to new drive...
3. Rename new drive with existing drive letter.
4. start sql.
My question is - will the change of drive letter work normally for cluster
installations or do i need to take any special care?
If the drive letter is the same, the original files and directories are put
back, and the account running SQL Server has permissions to the files then
SQL won't detect any difference and be fine. However,
the cluster service may be a different story.
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DD1F651A-F5D2-49B0-A220-3BD6343E815D@.microsoft.com...
>I want to add a new drive to replace an existing drive used by SQL
> server(cluster installation).
> My plan is to
> 1. stop sql related services.
> 2. copy sql db files to new drive...
> 3. Rename new drive with existing drive letter.
> 4. start sql.
> My question is - will the change of drive letter work normally for cluster
> installations or do i need to take any special care?
|||Hi
Changing a drive letter in a cluster becomes a lot more complicated as the
cluster services depend on it.
You have to between steps 2 and 3, remove the dependency in cluster manager,
then re-name the letter, establish the dependencies in cluster manager and
then start SQL Server.
It is best to take SQL Server and Agent offline, and then reboot each node
to make sure the groups and resources fail over correctly. Then bring SQL
Server online again.
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/
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DD1F651A-F5D2-49B0-A220-3BD6343E815D@.microsoft.com...
>I want to add a new drive to replace an existing drive used by SQL
> server(cluster installation).
> My plan is to
> 1. stop sql related services.
> 2. copy sql db files to new drive...
> 3. Rename new drive with existing drive letter.
> 4. start sql.
> My question is - will the change of drive letter work normally for cluster
> installations or do i need to take any special care?
sql

renaming database

I tried to renaming database using query analyser of sql
server 2000 but I got this error msg.
Server: Msg 5030, Level 16, State 2, Line 1
The database could not be exclusively locked to perform
the operation.
My sysntax was
sp_renamedb 'old_dbname', 'new_dbname'
How to handle this? what could be the solution?
Thanx
Dave
hi dave,
make sure no-one else is connected to the database, including you.
you can try:
use master
go
exec sp_renamedb ..........
--or (if sql 2000) you can try
alter database old_Database_name modify name = new_database_name
--if, still you get errors you can run following command,to disconnect other
users:
--note:it will rollback existing transaction
alter database <db_name> set single_user with rollback IMMEDIATE
Vishal Parkar
vgparkar@.yahoo.co.in | vgparkar@.hotmail.com
|||still same proble, bro...
dave
>--Original Message--
>hi dave,
>make sure no-one else is connected to the database,
including you.
>you can try:
>use master
>go
>exec sp_renamedb ..........
>--or (if sql 2000) you can try
>alter database old_Database_name modify name =
new_database_name
>--if, still you get errors you can run following
command,to disconnect other
>users:
>--note:it will rollback existing transaction
>alter database <db_name> set single_user with rollback
IMMEDIATE
>--
>Vishal Parkar
>vgparkar@.yahoo.co.in | vgparkar@.hotmail.com
>
>.
>
|||Try this. Stop the SQL Server from SQL Server Service Manager and Start
again, and then try to rename it.
Rohtash Kapoor
http://www.sqlmantra.com
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:28f5f01c4656d$493c0f50$a601280a@.phx.gbl...[vbcol=seagreen]
> still same proble, bro...
> dave
> including you.
> new_database_name
> command,to disconnect other
> IMMEDIATE
|||Hi,
Follow the below steps to rename a database in SQL server 2000.
1. Remove all the users connected to the database
alter database <dbname> set single_user with rollback immediate
2. Run the below command to rename the database
alter database <current_db_name> modify name=<new_db_name>
3. Set to multi user mode
alter database <dbname> set multi_user
Thanks
Hari
MCDBA
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:28e1e01c4654c$a8962ab0$a601280a@.phx.gbl...
> I tried to renaming database using query analyser of sql
> server 2000 but I got this error msg.
> Server: Msg 5030, Level 16, State 2, Line 1
> The database could not be exclusively locked to perform
> the operation.
> My sysntax was
> sp_renamedb 'old_dbname', 'new_dbname'
> How to handle this? what could be the solution?
> Thanx
> Dave
|||all you can do is restart the sql server service, which will clear out all
the connection to the db, and run
use master
go
exec sp_renamedb --
--or (if sql 2000) you can try
alter database old_Database_name modify name = new_database_name
Vishal Parkar
vgparkar@.yahoo.co.in | vgparkar@.hotmail.com
|||You could detach the database and then re-attach it with a different
name.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

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 database

Hi,
Is there any easy way to rename a database?
It can be done using SQL script or just
Enterprise Manager.
I'm using SQLServer 2000
Regards
Miroomust use T-SQL script, two means:
1.sp_renamedb dbold, dbnew
2.ALTER DATABASE dbold MODIFY NAME=dbnew
"Miroo_news" <miroo@.USUNTO.poczta.fm> wrote in message
news:bm09qr$78l$1@.atlantis.news.tpi.pl...
> Hi,
> Is there any easy way to rename a database?
> It can be done using SQL script or just
> Enterprise Manager.
> I'm using SQLServer 2000
> Regards
> Miroo|||U¿ytkownik "Henry" <qiuliang@.163.net> napisa³ w wiadomo¶ci
news:OyD5KTWjDHA.684@.TK2MSFTNGP09.phx.gbl...
> must use T-SQL script, two means:
> 2.ALTER DATABASE dbold MODIFY NAME=dbnew
Thank you, it works OK.
Regards,
Miroo

removing user

Hello,
I have a problem with removing an user on a SQLSERVER V7 base.
I can suppress the user, but it still exist for the role PUBLIC.
Can you help me ?Do you mean that you remove the user from the database, but they can still get in through Public, or are you getting an error when you try to delete the user?

blindman|||Hi...
What u mean by suppress the user...? What errror message u r getting?
U can remove user from User Roles still it will exists in Public. Do the user owns some objects ? guests are allowed in the DB ?

Cheers :)

Shaji

Originally posted by jleb
Hello,
I have a problem with removing an user on a SQLSERVER V7 base.

I can suppress the user, but it still exist for the role PUBLIC.

Can you help me ?|||I remove the user from the database, but it still exists whem I look the Public role.

Thank you fopr your help, I have found a solution with the command sp_revokedbaccess.

Originally posted by blindman
Do you mean that you remove the user from the database, but they can still get in through Public, or are you getting an error when you try to delete the user?

blindman

Removing SQLServer 2005 Express Registry Keys

MS update cannot install a Service Pack to SQL Server 2005 Express because a
component of an earlier version (a CTP, the Reporting Services component)
cannot be uninstalled. Can anyone tell me which set of registry keys I
should delete after removing SQL Server 2005 in order to reinstall on a
clean sustem?
Many thanks.Hi Andrew
"Andrew Chalk" wrote:

> MS update cannot install a Service Pack to SQL Server 2005 Express because
a
> component of an earlier version (a CTP, the Reporting Services component)
> cannot be uninstalled. Can anyone tell me which set of registry keys I
> should delete after removing SQL Server 2005 in order to reinstall on a
> clean sustem?
> Many thanks.
Do these help?
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
http://support.microsoft.com/kb/909967/
http://blogs.msdn.com/astebner/arch.../13/465401.aspx
John|||Thanks.This http://blogs.msdn.com/astebner/arch.../13/465401.aspx
had the brute force method that did it.
- A
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EC308ED0-5BEE-486D-9D66-573845FC5360@.microsoft.com...
> Hi Andrew
> "Andrew Chalk" wrote:
>
> Do these help?
> http://msdn2.microsoft.com/en-us/library/ms143505.aspx
> http://support.microsoft.com/kb/909967/
> http://blogs.msdn.com/astebner/arch.../13/465401.aspx
> John
>

Removing SQLServer 2005 Express Registry Keys

MS update cannot install a Service Pack to SQL Server 2005 Express because a
component of an earlier version (a CTP, the Reporting Services component)
cannot be uninstalled. Can anyone tell me which set of registry keys I
should delete after removing SQL Server 2005 in order to reinstall on a
clean sustem?
Many thanks.
Hi Andrew
"Andrew Chalk" wrote:

> MS update cannot install a Service Pack to SQL Server 2005 Express because a
> component of an earlier version (a CTP, the Reporting Services component)
> cannot be uninstalled. Can anyone tell me which set of registry keys I
> should delete after removing SQL Server 2005 in order to reinstall on a
> clean sustem?
> Many thanks.
Do these help?
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
http://support.microsoft.com/kb/909967/
http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
John
|||Thanks.This http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
had the brute force method that did it.
- A
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EC308ED0-5BEE-486D-9D66-573845FC5360@.microsoft.com...
> Hi Andrew
> "Andrew Chalk" wrote:
>
> Do these help?
> http://msdn2.microsoft.com/en-us/library/ms143505.aspx
> http://support.microsoft.com/kb/909967/
> http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
> John
>

Removing SQLServer 2005 Express Registry Keys

MS update cannot install a Service Pack to SQL Server 2005 Express because a
component of an earlier version (a CTP, the Reporting Services component)
cannot be uninstalled. Can anyone tell me which set of registry keys I
should delete after removing SQL Server 2005 in order to reinstall on a
clean sustem?
Many thanks.
Hi Andrew
"Andrew Chalk" wrote:

> MS update cannot install a Service Pack to SQL Server 2005 Express because a
> component of an earlier version (a CTP, the Reporting Services component)
> cannot be uninstalled. Can anyone tell me which set of registry keys I
> should delete after removing SQL Server 2005 in order to reinstall on a
> clean sustem?
> Many thanks.
Do these help?
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
http://support.microsoft.com/kb/909967/
http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
John
|||Thanks.This http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
had the brute force method that did it.
- A
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EC308ED0-5BEE-486D-9D66-573845FC5360@.microsoft.com...
> Hi Andrew
> "Andrew Chalk" wrote:
>
> Do these help?
> http://msdn2.microsoft.com/en-us/library/ms143505.aspx
> http://support.microsoft.com/kb/909967/
> http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
> John
>

Removing SQLServer 2005 Express Registry Keys

MS update cannot install a Service Pack to SQL Server 2005 Express because a
component of an earlier version (a CTP, the Reporting Services component)
cannot be uninstalled. Can anyone tell me which set of registry keys I
should delete after removing SQL Server 2005 in order to reinstall on a
clean sustem?
Many thanks.Hi Andrew
"Andrew Chalk" wrote:
> MS update cannot install a Service Pack to SQL Server 2005 Express because a
> component of an earlier version (a CTP, the Reporting Services component)
> cannot be uninstalled. Can anyone tell me which set of registry keys I
> should delete after removing SQL Server 2005 in order to reinstall on a
> clean sustem?
> Many thanks.
Do these help?
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
http://support.microsoft.com/kb/909967/
http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
John|||Thanks.This http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
had the brute force method that did it.
- A
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EC308ED0-5BEE-486D-9D66-573845FC5360@.microsoft.com...
> Hi Andrew
> "Andrew Chalk" wrote:
>> MS update cannot install a Service Pack to SQL Server 2005 Express
>> because a
>> component of an earlier version (a CTP, the Reporting Services component)
>> cannot be uninstalled. Can anyone tell me which set of registry keys I
>> should delete after removing SQL Server 2005 in order to reinstall on a
>> clean sustem?
>> Many thanks.
> Do these help?
> http://msdn2.microsoft.com/en-us/library/ms143505.aspx
> http://support.microsoft.com/kb/909967/
> http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx
> John
>

Removing Domain Controller status from a SQL server

Aloha -
I have a sick server (HOKU) which doubles as a domain controller and a SQL
server. The plan is to move SQL to a new server (SQL1), demote HOKU to a
member server, remove it from the domain then do away with it.
The plan is to demote it this weekend. Then in a couple weeks move the SQL
once testing is done. Is there danger in "de-domain controlering" a SQL
server that is used to being on a DC? At this point I know enough to know
that we're making a fairly major change, but I don't know enough to know
exactly what I am nervous about.
Hi
From a SQL Server point of view, I don't see any problems in demoting a SQL
server. SQL server don't use anything from the Domain Controller as such, so
as long as you have your domain fully functional there shouldn't be any
problems.
Depending on how your users connect to the databases, there might be some
fiddling around when you move the SQL server, since you most likely will
change the server name and/or IP adress.
Regards
Steen
Kahonu wrote:
> Aloha -
> I have a sick server (HOKU) which doubles as a domain controller and
> a SQL server. The plan is to move SQL to a new server (SQL1), demote
> HOKU to a member server, remove it from the domain then do away with
> it.
> The plan is to demote it this weekend. Then in a couple weeks move
> the SQL once testing is done. Is there danger in "de-domain
> controlering" a SQL server that is used to being on a DC? At this
> point I know enough to know that we're making a fairly major change,
> but I don't know enough to know exactly what I am nervous about.
|||Kahonu wrote on Wed, 1 Jun 2005 19:03:18 -0700:

> Aloha -
> I have a sick server (HOKU) which doubles as a domain controller and a SQL
> server. The plan is to move SQL to a new server (SQL1), demote HOKU to a
> member server, remove it from the domain then do away with it.
> The plan is to demote it this weekend. Then in a couple weeks move the SQL
> once testing is done. Is there danger in "de-domain controlering" a SQL
> server that is used to being on a DC? At this point I know enough to know
> that we're making a fairly major change, but I don't know enough to know
> exactly what I am nervous about.
I demoted a W2K Server to a member server with SQL Server 2000 just 2 weeks
ago, no ill effects as yet. I needed to rename the server prior to running
in production, and I'd be running it as a domain controller while migrating
from NT4 to 2K. The demotion was painless, it was the renaming that was the
fun part :\
Dan
|||I have also demoted as you are doing, and like the others had no problems...
In fact, it is a bad practice to put SQL on a domain controller anyway - so
you are doing a good thing and improving security by your actions as well.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Kahonu" <Kahonu@.discussions.microsoft.com> wrote in message
news:FE165EC2-B09B-4D40-9782-D8C54CB036C7@.microsoft.com...
> Aloha -
> I have a sick server (HOKU) which doubles as a domain controller and a SQL
> server. The plan is to move SQL to a new server (SQL1), demote HOKU to a
> member server, remove it from the domain then do away with it.
> The plan is to demote it this weekend. Then in a couple weeks move the SQL
> once testing is done. Is there danger in "de-domain controlering" a SQL
> server that is used to being on a DC? At this point I know enough to know
> that we're making a fairly major change, but I don't know enough to know
> exactly what I am nervous about.
>

Removing Domain Controller status from a SQL server

Aloha -
I have a sick server (HOKU) which doubles as a domain controller and a SQL
server. The plan is to move SQL to a new server (SQL1), demote HOKU to a
member server, remove it from the domain then do away with it.
The plan is to demote it this weekend. Then in a couple weeks move the SQL
once testing is done. Is there danger in "de-domain controlering" a SQL
server that is used to being on a DC? At this point I know enough to know
that we're making a fairly major change, but I don't know enough to know
exactly what I am nervous about.Hi
From a SQL Server point of view, I don't see any problems in demoting a SQL
server. SQL server don't use anything from the Domain Controller as such, so
as long as you have your domain fully functional there shouldn't be any
problems.
Depending on how your users connect to the databases, there might be some
fiddling around when you move the SQL server, since you most likely will
change the server name and/or IP adress.
Regards
Steen
Kahonu wrote:
> Aloha -
> I have a sick server (HOKU) which doubles as a domain controller and
> a SQL server. The plan is to move SQL to a new server (SQL1), demote
> HOKU to a member server, remove it from the domain then do away with
> it.
> The plan is to demote it this weekend. Then in a couple weeks move
> the SQL once testing is done. Is there danger in "de-domain
> controlering" a SQL server that is used to being on a DC? At this
> point I know enough to know that we're making a fairly major change,
> but I don't know enough to know exactly what I am nervous about.|||Kahonu wrote on Wed, 1 Jun 2005 19:03:18 -0700:

> Aloha -
> I have a sick server (HOKU) which doubles as a domain controller and a SQL
> server. The plan is to move SQL to a new server (SQL1), demote HOKU to a
> member server, remove it from the domain then do away with it.
> The plan is to demote it this weekend. Then in a couple weeks move the SQL
> once testing is done. Is there danger in "de-domain controlering" a SQL
> server that is used to being on a DC? At this point I know enough to know
> that we're making a fairly major change, but I don't know enough to know
> exactly what I am nervous about.
I demoted a W2K Server to a member server with SQL Server 2000 just 2 weeks
ago, no ill effects as yet. I needed to rename the server prior to running
in production, and I'd be running it as a domain controller while migrating
from NT4 to 2K. The demotion was painless, it was the renaming that was the
fun part :\
Dan|||I have also demoted as you are doing, and like the others had no problems...
In fact, it is a bad practice to put SQL on a domain controller anyway - so
you are doing a good thing and improving security by your actions as well.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Kahonu" <Kahonu@.discussions.microsoft.com> wrote in message
news:FE165EC2-B09B-4D40-9782-D8C54CB036C7@.microsoft.com...
> Aloha -
> I have a sick server (HOKU) which doubles as a domain controller and a SQL
> server. The plan is to move SQL to a new server (SQL1), demote HOKU to a
> member server, remove it from the domain then do away with it.
> The plan is to demote it this weekend. Then in a couple weeks move the SQL
> once testing is done. Is there danger in "de-domain controlering" a SQL
> server that is used to being on a DC? At this point I know enough to know
> that we're making a fairly major change, but I don't know enough to know
> exactly what I am nervous about.
>