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?
Friday, March 30, 2012
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
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 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?
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 domain
We have a small site where we want to rename the domain and bring it into
our domain.
current names are as
domainx.local -holds SQL server cluster
domainx.net -main domain
we want to bring domainx.local into the domainx.net AD.
will will rename and migrate. Are there any tools for SQL2005?
we were planning on using the microsoft domain rename tool and ADMT3.
Any other issues with SQL?
Regards
CC
SQL itself doesn't really care what domain it is in, as long as all of the
resources and servers it has to access are still accessible the way they
were before. The only thing you will have to update is the windows service
accounts if any of them are from AD and not the local machine. Will it be
renamed or are you moving to a new domain while the old domain remains up
for a short period of time? If the latter I would recommend setting up a
trust and switching the accounts, or understanding that you might have blips
in uptime/availability.
"Ned" <Cal@.obded.org> wrote in message
news:%231UNGh2ZIHA.2000@.TK2MSFTNGP05.phx.gbl...
> We have a small site where we want to rename the domain and bring it into
> our domain.
> current names are as
> domainx.local -holds SQL server cluster
> domainx.net -main domain
> we want to bring domainx.local into the domainx.net AD.
> will will rename and migrate. Are there any tools for SQL2005?
> we were planning on using the microsoft domain rename tool and ADMT3.
> Any other issues with SQL?
> Regards
> CC
>
|||Hi
I assume that the machine names for the SQL Servers are not changing?
If you have granted logins to domain accounts or groups then you may need to
change them see http://support.microsoft.com/kb/298897/
John
"Ned" wrote:
> We have a small site where we want to rename the domain and bring it into
> our domain.
> current names are as
> domainx.local -holds SQL server cluster
> domainx.net -main domain
> we want to bring domainx.local into the domainx.net AD.
> will will rename and migrate. Are there any tools for SQL2005?
> we were planning on using the microsoft domain rename tool and ADMT3.
> Any other issues with SQL?
> Regards
> CC
>
>
our domain.
current names are as
domainx.local -holds SQL server cluster
domainx.net -main domain
we want to bring domainx.local into the domainx.net AD.
will will rename and migrate. Are there any tools for SQL2005?
we were planning on using the microsoft domain rename tool and ADMT3.
Any other issues with SQL?
Regards
CC
SQL itself doesn't really care what domain it is in, as long as all of the
resources and servers it has to access are still accessible the way they
were before. The only thing you will have to update is the windows service
accounts if any of them are from AD and not the local machine. Will it be
renamed or are you moving to a new domain while the old domain remains up
for a short period of time? If the latter I would recommend setting up a
trust and switching the accounts, or understanding that you might have blips
in uptime/availability.
"Ned" <Cal@.obded.org> wrote in message
news:%231UNGh2ZIHA.2000@.TK2MSFTNGP05.phx.gbl...
> We have a small site where we want to rename the domain and bring it into
> our domain.
> current names are as
> domainx.local -holds SQL server cluster
> domainx.net -main domain
> we want to bring domainx.local into the domainx.net AD.
> will will rename and migrate. Are there any tools for SQL2005?
> we were planning on using the microsoft domain rename tool and ADMT3.
> Any other issues with SQL?
> Regards
> CC
>
|||Hi
I assume that the machine names for the SQL Servers are not changing?
If you have granted logins to domain accounts or groups then you may need to
change them see http://support.microsoft.com/kb/298897/
John
"Ned" wrote:
> We have a small site where we want to rename the domain and bring it into
> our domain.
> current names are as
> domainx.local -holds SQL server cluster
> domainx.net -main domain
> we want to bring domainx.local into the domainx.net AD.
> will will rename and migrate. Are there any tools for SQL2005?
> we were planning on using the microsoft domain rename tool and ADMT3.
> Any other issues with SQL?
> Regards
> CC
>
>
renaming domain
We have a small site where we want to rename the domain and bring it into
our domain.
current names are as
domainx.local -holds SQL server cluster
domainx.net -main domain
we want to bring domainx.local into the domainx.net AD.
will will rename and migrate. Are there any tools for SQL2005?
we were planning on using the microsoft domain rename tool and ADMT3.
Any other issues with SQL?
Regards
CCSQL itself doesn't really care what domain it is in, as long as all of the
resources and servers it has to access are still accessible the way they
were before. The only thing you will have to update is the windows service
accounts if any of them are from AD and not the local machine. Will it be
renamed or are you moving to a new domain while the old domain remains up
for a short period of time? If the latter I would recommend setting up a
trust and switching the accounts, or understanding that you might have blips
in uptime/availability.
"Ned" <Cal@.obded.org> wrote in message
news:%231UNGh2ZIHA.2000@.TK2MSFTNGP05.phx.gbl...
> We have a small site where we want to rename the domain and bring it into
> our domain.
> current names are as
> domainx.local -holds SQL server cluster
> domainx.net -main domain
> we want to bring domainx.local into the domainx.net AD.
> will will rename and migrate. Are there any tools for SQL2005?
> we were planning on using the microsoft domain rename tool and ADMT3.
> Any other issues with SQL?
> Regards
> CC
>|||Hi
I assume that the machine names for the SQL Servers are not changing?
If you have granted logins to domain accounts or groups then you may need to
change them see http://support.microsoft.com/kb/298897/
John
"Ned" wrote:
> We have a small site where we want to rename the domain and bring it into
> our domain.
> current names are as
> domainx.local -holds SQL server cluster
> domainx.net -main domain
> we want to bring domainx.local into the domainx.net AD.
> will will rename and migrate. Are there any tools for SQL2005?
> we were planning on using the microsoft domain rename tool and ADMT3.
> Any other issues with SQL?
> Regards
> CC
>
>
our domain.
current names are as
domainx.local -holds SQL server cluster
domainx.net -main domain
we want to bring domainx.local into the domainx.net AD.
will will rename and migrate. Are there any tools for SQL2005?
we were planning on using the microsoft domain rename tool and ADMT3.
Any other issues with SQL?
Regards
CCSQL itself doesn't really care what domain it is in, as long as all of the
resources and servers it has to access are still accessible the way they
were before. The only thing you will have to update is the windows service
accounts if any of them are from AD and not the local machine. Will it be
renamed or are you moving to a new domain while the old domain remains up
for a short period of time? If the latter I would recommend setting up a
trust and switching the accounts, or understanding that you might have blips
in uptime/availability.
"Ned" <Cal@.obded.org> wrote in message
news:%231UNGh2ZIHA.2000@.TK2MSFTNGP05.phx.gbl...
> We have a small site where we want to rename the domain and bring it into
> our domain.
> current names are as
> domainx.local -holds SQL server cluster
> domainx.net -main domain
> we want to bring domainx.local into the domainx.net AD.
> will will rename and migrate. Are there any tools for SQL2005?
> we were planning on using the microsoft domain rename tool and ADMT3.
> Any other issues with SQL?
> Regards
> CC
>|||Hi
I assume that the machine names for the SQL Servers are not changing?
If you have granted logins to domain accounts or groups then you may need to
change them see http://support.microsoft.com/kb/298897/
John
"Ned" wrote:
> We have a small site where we want to rename the domain and bring it into
> our domain.
> current names are as
> domainx.local -holds SQL server cluster
> domainx.net -main domain
> we want to bring domainx.local into the domainx.net AD.
> will will rename and migrate. Are there any tools for SQL2005?
> we were planning on using the microsoft domain rename tool and ADMT3.
> Any other issues with SQL?
> Regards
> CC
>
>
Renaming Destination in DTS
I searched, but couldn't find anything to match what I am looking for...
Basically, is there any way to tell DTS to create a new table each time that the backup is run? I am scheduling the backup for 1 hour intervals for 5 days, but need the databases that are backed up to be unique, so i would end up wiht 120 of them total.
Is there any way to do this through DTS? Or am I hosed?
Thanks in advanceYep, you can do it. You'll have to adapt what's in the links, but it does work. You can pass variables into a DTS job and have it alter execution each time it's run.
http://www.swynk.com/friends/green/textfile.asp
http://www.swynk.com/friends/green/DTSHowTo3.asp
http://www.sqldts.com/
http://www.dts2000.com/
Renaming databases with grace, any hint ?
Hi,
Later on, a consolidation process collect the data in Last_Known_Good versions of the databases.
I want to implement the following pattern (pseudo-code follows):
[for index in x different databases, where x is rather big]
- create database MyDatabase_#{index}_Temp launch a dedicated ssis package on this database if I detect no error, proudly rename MyDatabase_#{index}_Temp to MyDatabase_#{index}_Last_Known_Good (drop the last_known_good first if it exist)
Later on, a consolidation process collect the data in Last_Known_Good versions of the databases.
My question: what is the simpliest way to achieve the rename operation (step 3) ?
I have tried an "alter database #{old_database_name} modify name = #{new_database_name}", but it works only once: once renamed, the database keeps the old mdf and ldf filenames, and the next create database will choke on this.
I have also tried to rename the logical filenames with ALTER DATABASE XXX MODIFY FILE (NAME = YYY, NEWNAME = ZZZ) but it doesn't work either.
I'd like to avoid specifying absolute mdf and ldf filenames myself, is it possible ?
best,
Thibaut
The best method for what you describe is probably to DETACH the "last good" and ATTACH the "new" as the old name. Yes, you will need to know the file names.
|||Thanks Tom. Too bad I have to know the file names, this pattern is very useful...
Subscribe to:
Posts (Atom)