Can I move data and full text search files to another drive and change the drive letter?
My server's G: drive is rapidly running out of space. It mainly contains data files (*.mdf) for both system and user databases. The FullText Catalogs also exist on that drive.
IT added a much lager E: drive.
I would like to:
- shutdown SQL Server
- copy everything from G: to E:
- change the G: drive to X:
- change the E: drive to G:
- reboot
Will that cause any problems with SQL Server? At the end of the process all of the files will be on the G: drive; just not on the original G: drive.
sql-server sql-server-2005
asked Aug 8 '12 at 17:57
EliEli
45049
add a comment |
My server's G: drive is rapidly running out of space. It mainly contains data files (*.mdf) for both system and user databases. The FullText Catalogs also exist on that drive.
IT added a much lager E: drive.
I would like to:
- shutdown SQL Server
- copy everything from G: to E:
- change the G: drive to X:
- change the E: drive to G:
- reboot
Will that cause any problems with SQL Server? At the end of the process all of the files will be on the G: drive; just not on the original G: drive.
sql-server sql-server-2005
asked Aug 8 '12 at 17:57
EliEli
45049
add a comment |
My server's G: drive is rapidly running out of space. It mainly contains data files (*.mdf) for both system and user databases. The FullText Catalogs also exist on that drive.
IT added a much lager E: drive.
I would like to:
- shutdown SQL Server
- copy everything from G: to E:
- change the G: drive to X:
- change the E: drive to G:
- reboot
Will that cause any problems with SQL Server? At the end of the process all of the files will be on the G: drive; just not on the original G: drive.
sql-server sql-server-2005
asked Aug 8 '12 at 17:57
EliEli
45049
My server's G: drive is rapidly running out of space. It mainly contains data files (*.mdf) for both system and user databases. The FullText Catalogs also exist on that drive.
IT added a much lager E: drive.
I would like to:
- shutdown SQL Server
- copy everything from G: to E:
- change the G: drive to X:
- change the E: drive to G:
- reboot
Will that cause any problems with SQL Server? At the end of the process all of the files will be on the G: drive; just not on the original G: drive.
sql-server sql-server-2005
sql-server sql-server-2005
asked Aug 8 '12 at 17:57
EliEli
45049
asked Aug 8 '12 at 17:57
EliEli
45049
edited Aug 8 '12 at 18:17
Eli
asked Aug 8 '12 at 17:57
EliEli
45049
asked Aug 8 '12 at 17:57
EliEli
45049
asked Aug 8 '12 at 17:57
EliEli
45049
45049
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I just did something like this with my system databases for a SAN migration and it didn't seem to have any negative impact. Having said that, I tested it in a dev/test environment. Do you have an opportunity to test this in a dev/test environment?
Also, there's not much of a need to reboot. Just stop the services, do the move, and start the services.
One final consideration is that you copy the files appropriately. Managing NTFS permissions issues can be a real pain so use something like XCOPY (which is what I used) or RoboCopy to ensure that you preserve the integrity of those permissions.
edited 6 mins ago
Paul White♦
51k14278450
answered Aug 8 '12 at 18:32
swasheckswasheck
7,66333882
We don't have enough drive/space on the dev server to test. However, this is a standby server for production. The main production server already has a large G: drive. Thanks for the permissions tip. I'll use xcopy with /O /X /E /H /K.
– Eli
Aug 8 '12 at 18:56
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f22196%2fcan-i-move-data-and-full-text-search-files-to-another-drive-and-change-the-drive%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I just did something like this with my system databases for a SAN migration and it didn't seem to have any negative impact. Having said that, I tested it in a dev/test environment. Do you have an opportunity to test this in a dev/test environment?
Also, there's not much of a need to reboot. Just stop the services, do the move, and start the services.
One final consideration is that you copy the files appropriately. Managing NTFS permissions issues can be a real pain so use something like XCOPY (which is what I used) or RoboCopy to ensure that you preserve the integrity of those permissions.
edited 6 mins ago
Paul White♦
51k14278450
answered Aug 8 '12 at 18:32
swasheckswasheck
7,66333882
We don't have enough drive/space on the dev server to test. However, this is a standby server for production. The main production server already has a large G: drive. Thanks for the permissions tip. I'll use xcopy with /O /X /E /H /K.
– Eli
Aug 8 '12 at 18:56
add a comment |
I just did something like this with my system databases for a SAN migration and it didn't seem to have any negative impact. Having said that, I tested it in a dev/test environment. Do you have an opportunity to test this in a dev/test environment?
Also, there's not much of a need to reboot. Just stop the services, do the move, and start the services.
One final consideration is that you copy the files appropriately. Managing NTFS permissions issues can be a real pain so use something like XCOPY (which is what I used) or RoboCopy to ensure that you preserve the integrity of those permissions.
edited 6 mins ago
Paul White♦
51k14278450
answered Aug 8 '12 at 18:32
swasheckswasheck
7,66333882
We don't have enough drive/space on the dev server to test. However, this is a standby server for production. The main production server already has a large G: drive. Thanks for the permissions tip. I'll use xcopy with /O /X /E /H /K.
– Eli
Aug 8 '12 at 18:56
add a comment |
I just did something like this with my system databases for a SAN migration and it didn't seem to have any negative impact. Having said that, I tested it in a dev/test environment. Do you have an opportunity to test this in a dev/test environment?
Also, there's not much of a need to reboot. Just stop the services, do the move, and start the services.
One final consideration is that you copy the files appropriately. Managing NTFS permissions issues can be a real pain so use something like XCOPY (which is what I used) or RoboCopy to ensure that you preserve the integrity of those permissions.
edited 6 mins ago
Paul White♦
51k14278450
answered Aug 8 '12 at 18:32
swasheckswasheck
7,66333882
I just did something like this with my system databases for a SAN migration and it didn't seem to have any negative impact. Having said that, I tested it in a dev/test environment. Do you have an opportunity to test this in a dev/test environment?
Also, there's not much of a need to reboot. Just stop the services, do the move, and start the services.
One final consideration is that you copy the files appropriately. Managing NTFS permissions issues can be a real pain so use something like XCOPY (which is what I used) or RoboCopy to ensure that you preserve the integrity of those permissions.
edited 6 mins ago
Paul White♦
51k14278450
answered Aug 8 '12 at 18:32
swasheckswasheck
7,66333882
edited 6 mins ago
Paul White♦
51k14278450
edited 6 mins ago
Paul White♦
51k14278450
edited 6 mins ago
Paul White♦
51k14278450
51k14278450
answered Aug 8 '12 at 18:32
swasheckswasheck
7,66333882
answered Aug 8 '12 at 18:32
swasheckswasheck
7,66333882
answered Aug 8 '12 at 18:32
swasheckswasheck
7,66333882
7,66333882
We don't have enough drive/space on the dev server to test. However, this is a standby server for production. The main production server already has a large G: drive. Thanks for the permissions tip. I'll use xcopy with /O /X /E /H /K.
– Eli
Aug 8 '12 at 18:56
add a comment |
We don't have enough drive/space on the dev server to test. However, this is a standby server for production. The main production server already has a large G: drive. Thanks for the permissions tip. I'll use xcopy with /O /X /E /H /K.
– Eli
Aug 8 '12 at 18:56
We don't have enough drive/space on the dev server to test. However, this is a standby server for production. The main production server already has a large G: drive. Thanks for the permissions tip. I'll use xcopy with /O /X /E /H /K.
– Eli
Aug 8 '12 at 18:56
We don't have enough drive/space on the dev server to test. However, this is a standby server for production. The main production server already has a large G: drive. Thanks for the permissions tip. I'll use xcopy with /O /X /E /H /K.
– Eli
Aug 8 '12 at 18:56
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f22196%2fcan-i-move-data-and-full-text-search-files-to-another-drive-and-change-the-drive%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
