Secondary filegroup for Full Text Index only - rebuild when lost
Here's our config:
We have all our data in PRIMARY file group
We have our Full Text Index in another SECONDARY file group which resides on a very fast (but very unreliable) SSD drive. By "unreliable" I mean - it's a Amazon cloud server temporary drive (can be entirely lost in case of emergency restart/hardware failure).
Full-text index is not critical and we're ready to lose it completely as we can obviously rebuild it from scratch.
The question is: is there a way to revive the database in case the secondary file group is 100% lost, without going through the full backup/restore cycle? Like, simply delete the lost file group, then recreate it, then rebuild the index.
(We do have regular full database backups, log backups etc. etc. etc. so we can "restore to the point in time" but this implies long outage)
P.S. Also, any thoughts on how viable our approach is would be very much appreciated.
sql-server backup full-text-search filegroups
asked Nov 17 '18 at 12:32
jitbitjitbit
24828
add a comment |
Here's our config:
We have all our data in PRIMARY file group
We have our Full Text Index in another SECONDARY file group which resides on a very fast (but very unreliable) SSD drive. By "unreliable" I mean - it's a Amazon cloud server temporary drive (can be entirely lost in case of emergency restart/hardware failure).
Full-text index is not critical and we're ready to lose it completely as we can obviously rebuild it from scratch.
The question is: is there a way to revive the database in case the secondary file group is 100% lost, without going through the full backup/restore cycle? Like, simply delete the lost file group, then recreate it, then rebuild the index.
(We do have regular full database backups, log backups etc. etc. etc. so we can "restore to the point in time" but this implies long outage)
P.S. Also, any thoughts on how viable our approach is would be very much appreciated.
sql-server backup full-text-search filegroups
asked Nov 17 '18 at 12:32
jitbitjitbit
24828
Are you using a Azure VM and your Full Text Index is in D (temporary) drive?
– SqlWorldWide
Nov 17 '18 at 12:46
@SqlWorldWide we're using Amazon VM ("EC2") and yes, the index is on the temporary drive
– jitbit
Nov 17 '18 at 12:59
I know for Azure VM only thing we put is tempdb and have a script to create the folder on reboot before starting SQL Server. It is clearly mentionedThis temporary storage must not be used to store data that you are not willing to lose.
– SqlWorldWide
Nov 17 '18 at 13:09
@SqlWorldWide yes! we do exactly the same (tempdb, script etc). The thing is - WE ARE ready to lose the full text index. The only concern is - losing the secondary filegroup may put the database in some "funky" state, that is complicate to recover from...
– jitbit
Nov 17 '18 at 13:13
add a comment |
Here's our config:
We have all our data in PRIMARY file group
We have our Full Text Index in another SECONDARY file group which resides on a very fast (but very unreliable) SSD drive. By "unreliable" I mean - it's a Amazon cloud server temporary drive (can be entirely lost in case of emergency restart/hardware failure).
Full-text index is not critical and we're ready to lose it completely as we can obviously rebuild it from scratch.
The question is: is there a way to revive the database in case the secondary file group is 100% lost, without going through the full backup/restore cycle? Like, simply delete the lost file group, then recreate it, then rebuild the index.
(We do have regular full database backups, log backups etc. etc. etc. so we can "restore to the point in time" but this implies long outage)
P.S. Also, any thoughts on how viable our approach is would be very much appreciated.
sql-server backup full-text-search filegroups
asked Nov 17 '18 at 12:32
jitbitjitbit
24828
Here's our config:
We have all our data in PRIMARY file group
We have our Full Text Index in another SECONDARY file group which resides on a very fast (but very unreliable) SSD drive. By "unreliable" I mean - it's a Amazon cloud server temporary drive (can be entirely lost in case of emergency restart/hardware failure).
Full-text index is not critical and we're ready to lose it completely as we can obviously rebuild it from scratch.
The question is: is there a way to revive the database in case the secondary file group is 100% lost, without going through the full backup/restore cycle? Like, simply delete the lost file group, then recreate it, then rebuild the index.
(We do have regular full database backups, log backups etc. etc. etc. so we can "restore to the point in time" but this implies long outage)
P.S. Also, any thoughts on how viable our approach is would be very much appreciated.
sql-server backup full-text-search filegroups
sql-server backup full-text-search filegroups
asked Nov 17 '18 at 12:32
jitbitjitbit
24828
asked Nov 17 '18 at 12:32
jitbitjitbit
24828
edited Nov 17 '18 at 13:53
jitbit
asked Nov 17 '18 at 12:32
jitbitjitbit
24828
asked Nov 17 '18 at 12:32
jitbitjitbit
24828
asked Nov 17 '18 at 12:32
jitbitjitbit
24828
24828
Are you using a Azure VM and your Full Text Index is in D (temporary) drive?
– SqlWorldWide
Nov 17 '18 at 12:46
@SqlWorldWide we're using Amazon VM ("EC2") and yes, the index is on the temporary drive
– jitbit
Nov 17 '18 at 12:59
I know for Azure VM only thing we put is tempdb and have a script to create the folder on reboot before starting SQL Server. It is clearly mentionedThis temporary storage must not be used to store data that you are not willing to lose.
– SqlWorldWide
Nov 17 '18 at 13:09
@SqlWorldWide yes! we do exactly the same (tempdb, script etc). The thing is - WE ARE ready to lose the full text index. The only concern is - losing the secondary filegroup may put the database in some "funky" state, that is complicate to recover from...
– jitbit
Nov 17 '18 at 13:13
add a comment |
Are you using a Azure VM and your Full Text Index is in D (temporary) drive?
– SqlWorldWide
Nov 17 '18 at 12:46
@SqlWorldWide we're using Amazon VM ("EC2") and yes, the index is on the temporary drive
– jitbit
Nov 17 '18 at 12:59
I know for Azure VM only thing we put is tempdb and have a script to create the folder on reboot before starting SQL Server. It is clearly mentionedThis temporary storage must not be used to store data that you are not willing to lose.
– SqlWorldWide
Nov 17 '18 at 13:09
@SqlWorldWide yes! we do exactly the same (tempdb, script etc). The thing is - WE ARE ready to lose the full text index. The only concern is - losing the secondary filegroup may put the database in some "funky" state, that is complicate to recover from...
– jitbit
Nov 17 '18 at 13:13
Are you using a Azure VM and your Full Text Index is in D (temporary) drive?
– SqlWorldWide
Nov 17 '18 at 12:46
Are you using a Azure VM and your Full Text Index is in D (temporary) drive?
– SqlWorldWide
Nov 17 '18 at 12:46
@SqlWorldWide we're using Amazon VM ("EC2") and yes, the index is on the temporary drive
– jitbit
Nov 17 '18 at 12:59
@SqlWorldWide we're using Amazon VM ("EC2") and yes, the index is on the temporary drive
– jitbit
Nov 17 '18 at 12:59
I know for Azure VM only thing we put is tempdb and have a script to create the folder on reboot before starting SQL Server. It is clearly mentioned
This temporary storage must not be used to store data that you are not willing to lose.– SqlWorldWide
Nov 17 '18 at 13:09
I know for Azure VM only thing we put is tempdb and have a script to create the folder on reboot before starting SQL Server. It is clearly mentioned
This temporary storage must not be used to store data that you are not willing to lose.– SqlWorldWide
Nov 17 '18 at 13:09
@SqlWorldWide yes! we do exactly the same (tempdb, script etc). The thing is - WE ARE ready to lose the full text index. The only concern is - losing the secondary filegroup may put the database in some "funky" state, that is complicate to recover from...
– jitbit
Nov 17 '18 at 13:13
@SqlWorldWide yes! we do exactly the same (tempdb, script etc). The thing is - WE ARE ready to lose the full text index. The only concern is - losing the secondary filegroup may put the database in some "funky" state, that is complicate to recover from...
– jitbit
Nov 17 '18 at 13:13
add a comment |
1 Answer
1
active
oldest
votes
(answering my own question)
OK, so we ran a simulation - what will happen if we lose the secondary filegroup file?
Not good.
The database gets stuck in recovery mode and you can't do anything about it - you can't set the "emergency" mode, you can't change it to "single_user" mode - nothing. Basically, every command you run throws an error Unable to open the physical file "xxx.mdf". Operating system error 2: "2 (The system cannot find the file specified.)
The only solution is to restore the database. But "rebuilding" a secondary filegroup won't work, even if there's only a fulltext index in it.
answered 5 hours ago
jitbitjitbit
24828
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%2f222781%2fsecondary-filegroup-for-full-text-index-only-rebuild-when-lost%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
(answering my own question)
OK, so we ran a simulation - what will happen if we lose the secondary filegroup file?
Not good.
The database gets stuck in recovery mode and you can't do anything about it - you can't set the "emergency" mode, you can't change it to "single_user" mode - nothing. Basically, every command you run throws an error Unable to open the physical file "xxx.mdf". Operating system error 2: "2 (The system cannot find the file specified.)
The only solution is to restore the database. But "rebuilding" a secondary filegroup won't work, even if there's only a fulltext index in it.
answered 5 hours ago
jitbitjitbit
24828
add a comment |
(answering my own question)
OK, so we ran a simulation - what will happen if we lose the secondary filegroup file?
Not good.
The database gets stuck in recovery mode and you can't do anything about it - you can't set the "emergency" mode, you can't change it to "single_user" mode - nothing. Basically, every command you run throws an error Unable to open the physical file "xxx.mdf". Operating system error 2: "2 (The system cannot find the file specified.)
The only solution is to restore the database. But "rebuilding" a secondary filegroup won't work, even if there's only a fulltext index in it.
answered 5 hours ago
jitbitjitbit
24828
add a comment |
(answering my own question)
OK, so we ran a simulation - what will happen if we lose the secondary filegroup file?
Not good.
The database gets stuck in recovery mode and you can't do anything about it - you can't set the "emergency" mode, you can't change it to "single_user" mode - nothing. Basically, every command you run throws an error Unable to open the physical file "xxx.mdf". Operating system error 2: "2 (The system cannot find the file specified.)
The only solution is to restore the database. But "rebuilding" a secondary filegroup won't work, even if there's only a fulltext index in it.
answered 5 hours ago
jitbitjitbit
24828
(answering my own question)
OK, so we ran a simulation - what will happen if we lose the secondary filegroup file?
Not good.
The database gets stuck in recovery mode and you can't do anything about it - you can't set the "emergency" mode, you can't change it to "single_user" mode - nothing. Basically, every command you run throws an error Unable to open the physical file "xxx.mdf". Operating system error 2: "2 (The system cannot find the file specified.)
The only solution is to restore the database. But "rebuilding" a secondary filegroup won't work, even if there's only a fulltext index in it.
answered 5 hours ago
jitbitjitbit
24828
answered 5 hours ago
jitbitjitbit
24828
answered 5 hours ago
jitbitjitbit
24828
answered 5 hours ago
jitbitjitbit
24828
24828
add a comment |
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%2f222781%2fsecondary-filegroup-for-full-text-index-only-rebuild-when-lost%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
Are you using a Azure VM and your Full Text Index is in D (temporary) drive?
– SqlWorldWide
Nov 17 '18 at 12:46
@SqlWorldWide we're using Amazon VM ("EC2") and yes, the index is on the temporary drive
– jitbit
Nov 17 '18 at 12:59
I know for Azure VM only thing we put is tempdb and have a script to create the folder on reboot before starting SQL Server. It is clearly mentioned
This temporary storage must not be used to store data that you are not willing to lose.– SqlWorldWide
Nov 17 '18 at 13:09
@SqlWorldWide yes! we do exactly the same (tempdb, script etc). The thing is - WE ARE ready to lose the full text index. The only concern is - losing the secondary filegroup may put the database in some "funky" state, that is complicate to recover from...
– jitbit
Nov 17 '18 at 13:13