March 21, 2013 at 12:48 am
hi,
We have a best practice in BOL that
"We need to have a separate File Group for the User data".
Is the below statement is true:
If there is any corruption while writing the data to PRIMARY File Group's files the database will not available to access. We can make the Database available by adding Secondary FG and placing the data to this Group.
please clarify.
🙂
March 21, 2013 at 3:35 am
SQL* (3/21/2013)
If there is any corruption while writing the data to PRIMARY File Group's files the database will not available to access. We can make the Database available by adding Secondary FG and placing the data to this Group.
No, absolutely not. If there's corruption in the primary filegroup then you need to restore or repair the database, restore preferred in most cases.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 22, 2013 at 12:01 am
GilaMonster (3/21/2013)
SQL* (3/21/2013)
If there is any corruption while writing the data to PRIMARY File Group's files the database will not available to access. We can make the Database available by adding Secondary FG and placing the data to this Group.No, absolutely not. If there's corruption in the primary filegroup then you need to restore or repair the database, restore preferred in most cases.
I think i have asked the question wrongly, here
Two cases
1. With only Primary File Group.
The user data will be written to the Primary File Group, if there is an error while writing, Is this database will be available?
2. With Primary and a Secondary.
If we write all the user data to secondary File Group, and if there is any error while writing the data, Is this database will be available?
Thanks
🙂
March 22, 2013 at 3:25 am
SQL* (3/22/2013)
The user data will be written to the Primary File Group, if there is an error while writing, Is this database will be available?
Maybe. Depends what the error is. If it's severe enough that SQL marks the database suspect, then no.
2. With Primary and a Secondary.
If we write all the user data to secondary File Group, and if there is any error while writing the data, Is this database will be available?
Maybe. Depends what the error is. If it's severe enough that SQL marks the database suspect, then no.
File groups aren't a protection against losing the database to corruption
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply