SQL Server placement of master database files vs resource database filesWhere is the information about what files each database stored for SQL Server 2008 R2SQL Server reports for managementRelocate all files to folder checkbox unavailable sql server 2012Optimal placement of tempdb, mdf and ldf files in SQL Server 2012 on SSD's?I lost my database in SQL server 2008 R2Is is possible to recover a database from the 'raw' files (.mdf and .ldf) of the old server to a new SQL Server instance on a new server?Open .mdf and .ldf files in Microsoft SQL Server without attachOn SQL Server 2017 (Linux), where is the Resource Database persisted (located on disk)?SQL Server 2017 Installation issuesRestoring AdventureWorks2014 Database to SQL Server 2017
Rivers without rain
Re-entry to Germany after vacation using blue card
How to prevent z-fighting in OpenSCAD?
Overlay of two functions leaves gaps
Is Diceware more secure than a long passphrase?
Can I criticise the more senior developers around me for not writing clean code?
Extension of 2-adic valuation to the real numbers
Elements other than carbon that can form many different compounds by bonding to themselves?
How come there are so many candidates for the 2020 Democratic party presidential nomination?
Mistake in years of experience in resume?
Could the terminal length of components like resistors be reduced?
Checks user level and limit the data before saving it to mongoDB
Dynamic SOQL query relationship with field visibility for Users
How did Captain America manage to do this?
Converting a sprinkler system's 24V AC outputs to 3.3V DC logic inputs
What are the steps to solving this definite integral?
Is there a way to generate a list of distinct numbers such that no two subsets ever have an equal sum?
Does a large simulator bay have standard public address announcements?
A Note on N!
How to fry ground beef so it is well-browned
Why was the Spitfire's elliptical wing almost uncopied by other aircraft of World War 2?
Was there a shared-world project before "Thieves World"?
How much cash can I safely carry into the USA and avoid civil forfeiture?
Alignment of various blocks in tikz
SQL Server placement of master database files vs resource database files
Where is the information about what files each database stored for SQL Server 2008 R2SQL Server reports for managementRelocate all files to folder checkbox unavailable sql server 2012Optimal placement of tempdb, mdf and ldf files in SQL Server 2012 on SSD's?I lost my database in SQL server 2008 R2Is is possible to recover a database from the 'raw' files (.mdf and .ldf) of the old server to a new SQL Server instance on a new server?Open .mdf and .ldf files in Microsoft SQL Server without attachOn SQL Server 2017 (Linux), where is the Resource Database persisted (located on disk)?SQL Server 2017 Installation issuesRestoring AdventureWorks2014 Database to SQL Server 2017
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
In a post on SqlServerCentral.com, it is mentioned by several people that the files for the Resource database (mssqlsystemresource.mdf and ldf) should be placed in the same folder as the master database file. This was for SQL Server 2005. Is this still a recommendation when it comes to SQL Server 2017? I tried looking in BOL, but could not find any mention of this there.
sql-server sql-server-2017
asked Apr 23 at 12:40
GHauanGHauan
318214
add a comment |
In a post on SqlServerCentral.com, it is mentioned by several people that the files for the Resource database (mssqlsystemresource.mdf and ldf) should be placed in the same folder as the master database file. This was for SQL Server 2005. Is this still a recommendation when it comes to SQL Server 2017? I tried looking in BOL, but could not find any mention of this there.
sql-server sql-server-2017
asked Apr 23 at 12:40
GHauanGHauan
318214
add a comment |
In a post on SqlServerCentral.com, it is mentioned by several people that the files for the Resource database (mssqlsystemresource.mdf and ldf) should be placed in the same folder as the master database file. This was for SQL Server 2005. Is this still a recommendation when it comes to SQL Server 2017? I tried looking in BOL, but could not find any mention of this there.
sql-server sql-server-2017
asked Apr 23 at 12:40
GHauanGHauan
318214
In a post on SqlServerCentral.com, it is mentioned by several people that the files for the Resource database (mssqlsystemresource.mdf and ldf) should be placed in the same folder as the master database file. This was for SQL Server 2005. Is this still a recommendation when it comes to SQL Server 2017? I tried looking in BOL, but could not find any mention of this there.
sql-server sql-server-2017
sql-server sql-server-2017
asked Apr 23 at 12:40
GHauanGHauan
318214
asked Apr 23 at 12:40
GHauanGHauan
318214
asked Apr 23 at 12:40
GHauanGHauan
318214
asked Apr 23 at 12:40
GHauanGHauan
318214
asked Apr 23 at 12:40
GHauanGHauan
318214
318214
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Totally agree with what George has mentioned, just trying to shed some more light to make it clear.
For SQL Server 2005
You were allowed to move resource database. If you read SQL Server 2005 Master Database Document it says
The Resource database depends on the location of the master database. If you move the master database, you must also move the Resource database to the same location.
But this caused problem during service pack upgrade when users started moving it along with master database. The issue came while applying SP/CU which eventually failed because resource database was moved.
For SQL Server 2008 and above.
This was then fixed by MS and they changed the whole thing such that "user is not allowed to change resource database location" and this is why it was moved to <drive>:Program FilesMicrosoft SQL ServerMSSQL<version>.<instance_name>MSSQLBinnfolder along with other binaries, people normally do not touch contents of BINN folder. It's specifically in BINN folder because it does not contains any USER data only information related to SQL Server.
Yes there was some discrepancy in BOL documents which was later fixed. I wrote an article on this please read Should We Move Resource Database
Moral: Do not move resource database
answered Apr 23 at 13:19
ShankyShanky
14.7k32144
add a comment |
According to the docs
changing the location of the resource database is not supported or recommended.
It would also appear that a static path is produced for the location of the resource database in the form of
<drive>:Program FilesMicrosoft SQL ServerMSSQL<version>.<instance_name>MSSQLBinn
It would appear there is neither a supported path to change the locations of the resource database files, nor is it recommended to do so.
answered Apr 23 at 12:45
George.PalaciosGeorge.Palacios
2,765826
Yes, I noticed that as well (maybe should have said so in my post), but in the link there is mentioned a way to move it (from BOL they say), that is why I got a bit worried. We also have an instance where the two are located in different folders and have been so for years without any problems, but I don't think we have tried upgrading inplace for such a setup. (And that is when the problems will arise according to the link.)
– GHauan
Apr 23 at 13:07
George. Your answer was helpful, but the one from Shanky was a bit more explanatory (if that is a word), so I change the accepted answer to his.
– GHauan
Apr 23 at 14:30
@GHauan absolutely no problem with that - I would suggest in future potentially make your question a bit clearer? IMO I answered the question directly.
– George.Palacios
Apr 23 at 15:00
You are right, my bad. Thank you for taking the time to answer.
– GHauan
yesterday
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%2f235469%2fsql-server-placement-of-master-database-files-vs-resource-database-files%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Totally agree with what George has mentioned, just trying to shed some more light to make it clear.
For SQL Server 2005
You were allowed to move resource database. If you read SQL Server 2005 Master Database Document it says
The Resource database depends on the location of the master database. If you move the master database, you must also move the Resource database to the same location.
But this caused problem during service pack upgrade when users started moving it along with master database. The issue came while applying SP/CU which eventually failed because resource database was moved.
For SQL Server 2008 and above.
This was then fixed by MS and they changed the whole thing such that "user is not allowed to change resource database location" and this is why it was moved to <drive>:Program FilesMicrosoft SQL ServerMSSQL<version>.<instance_name>MSSQLBinnfolder along with other binaries, people normally do not touch contents of BINN folder. It's specifically in BINN folder because it does not contains any USER data only information related to SQL Server.
Yes there was some discrepancy in BOL documents which was later fixed. I wrote an article on this please read Should We Move Resource Database
Moral: Do not move resource database
answered Apr 23 at 13:19
ShankyShanky
14.7k32144
add a comment |
Totally agree with what George has mentioned, just trying to shed some more light to make it clear.
For SQL Server 2005
You were allowed to move resource database. If you read SQL Server 2005 Master Database Document it says
The Resource database depends on the location of the master database. If you move the master database, you must also move the Resource database to the same location.
But this caused problem during service pack upgrade when users started moving it along with master database. The issue came while applying SP/CU which eventually failed because resource database was moved.
For SQL Server 2008 and above.
This was then fixed by MS and they changed the whole thing such that "user is not allowed to change resource database location" and this is why it was moved to <drive>:Program FilesMicrosoft SQL ServerMSSQL<version>.<instance_name>MSSQLBinnfolder along with other binaries, people normally do not touch contents of BINN folder. It's specifically in BINN folder because it does not contains any USER data only information related to SQL Server.
Yes there was some discrepancy in BOL documents which was later fixed. I wrote an article on this please read Should We Move Resource Database
Moral: Do not move resource database
answered Apr 23 at 13:19
ShankyShanky
14.7k32144
add a comment |
Totally agree with what George has mentioned, just trying to shed some more light to make it clear.
For SQL Server 2005
You were allowed to move resource database. If you read SQL Server 2005 Master Database Document it says
The Resource database depends on the location of the master database. If you move the master database, you must also move the Resource database to the same location.
But this caused problem during service pack upgrade when users started moving it along with master database. The issue came while applying SP/CU which eventually failed because resource database was moved.
For SQL Server 2008 and above.
This was then fixed by MS and they changed the whole thing such that "user is not allowed to change resource database location" and this is why it was moved to <drive>:Program FilesMicrosoft SQL ServerMSSQL<version>.<instance_name>MSSQLBinnfolder along with other binaries, people normally do not touch contents of BINN folder. It's specifically in BINN folder because it does not contains any USER data only information related to SQL Server.
Yes there was some discrepancy in BOL documents which was later fixed. I wrote an article on this please read Should We Move Resource Database
Moral: Do not move resource database
answered Apr 23 at 13:19
ShankyShanky
14.7k32144
Totally agree with what George has mentioned, just trying to shed some more light to make it clear.
For SQL Server 2005
You were allowed to move resource database. If you read SQL Server 2005 Master Database Document it says
The Resource database depends on the location of the master database. If you move the master database, you must also move the Resource database to the same location.
But this caused problem during service pack upgrade when users started moving it along with master database. The issue came while applying SP/CU which eventually failed because resource database was moved.
For SQL Server 2008 and above.
This was then fixed by MS and they changed the whole thing such that "user is not allowed to change resource database location" and this is why it was moved to <drive>:Program FilesMicrosoft SQL ServerMSSQL<version>.<instance_name>MSSQLBinnfolder along with other binaries, people normally do not touch contents of BINN folder. It's specifically in BINN folder because it does not contains any USER data only information related to SQL Server.
Yes there was some discrepancy in BOL documents which was later fixed. I wrote an article on this please read Should We Move Resource Database
Moral: Do not move resource database
answered Apr 23 at 13:19
ShankyShanky
14.7k32144
edited Apr 23 at 13:26
answered Apr 23 at 13:19
ShankyShanky
14.7k32144
answered Apr 23 at 13:19
ShankyShanky
14.7k32144
answered Apr 23 at 13:19
ShankyShanky
14.7k32144
14.7k32144
add a comment |
add a comment |
According to the docs
changing the location of the resource database is not supported or recommended.
It would also appear that a static path is produced for the location of the resource database in the form of
<drive>:Program FilesMicrosoft SQL ServerMSSQL<version>.<instance_name>MSSQLBinn
It would appear there is neither a supported path to change the locations of the resource database files, nor is it recommended to do so.
answered Apr 23 at 12:45
George.PalaciosGeorge.Palacios
2,765826
Yes, I noticed that as well (maybe should have said so in my post), but in the link there is mentioned a way to move it (from BOL they say), that is why I got a bit worried. We also have an instance where the two are located in different folders and have been so for years without any problems, but I don't think we have tried upgrading inplace for such a setup. (And that is when the problems will arise according to the link.)
– GHauan
Apr 23 at 13:07
George. Your answer was helpful, but the one from Shanky was a bit more explanatory (if that is a word), so I change the accepted answer to his.
– GHauan
Apr 23 at 14:30
@GHauan absolutely no problem with that - I would suggest in future potentially make your question a bit clearer? IMO I answered the question directly.
– George.Palacios
Apr 23 at 15:00
You are right, my bad. Thank you for taking the time to answer.
– GHauan
yesterday
add a comment |
According to the docs
changing the location of the resource database is not supported or recommended.
It would also appear that a static path is produced for the location of the resource database in the form of
<drive>:Program FilesMicrosoft SQL ServerMSSQL<version>.<instance_name>MSSQLBinn
It would appear there is neither a supported path to change the locations of the resource database files, nor is it recommended to do so.
answered Apr 23 at 12:45
George.PalaciosGeorge.Palacios
2,765826
Yes, I noticed that as well (maybe should have said so in my post), but in the link there is mentioned a way to move it (from BOL they say), that is why I got a bit worried. We also have an instance where the two are located in different folders and have been so for years without any problems, but I don't think we have tried upgrading inplace for such a setup. (And that is when the problems will arise according to the link.)
– GHauan
Apr 23 at 13:07
George. Your answer was helpful, but the one from Shanky was a bit more explanatory (if that is a word), so I change the accepted answer to his.
– GHauan
Apr 23 at 14:30
@GHauan absolutely no problem with that - I would suggest in future potentially make your question a bit clearer? IMO I answered the question directly.
– George.Palacios
Apr 23 at 15:00
You are right, my bad. Thank you for taking the time to answer.
– GHauan
yesterday
add a comment |
According to the docs
changing the location of the resource database is not supported or recommended.
It would also appear that a static path is produced for the location of the resource database in the form of
<drive>:Program FilesMicrosoft SQL ServerMSSQL<version>.<instance_name>MSSQLBinn
It would appear there is neither a supported path to change the locations of the resource database files, nor is it recommended to do so.
answered Apr 23 at 12:45
George.PalaciosGeorge.Palacios
2,765826
According to the docs
changing the location of the resource database is not supported or recommended.
It would also appear that a static path is produced for the location of the resource database in the form of
<drive>:Program FilesMicrosoft SQL ServerMSSQL<version>.<instance_name>MSSQLBinn
It would appear there is neither a supported path to change the locations of the resource database files, nor is it recommended to do so.
answered Apr 23 at 12:45
George.PalaciosGeorge.Palacios
2,765826
answered Apr 23 at 12:45
George.PalaciosGeorge.Palacios
2,765826
answered Apr 23 at 12:45
George.PalaciosGeorge.Palacios
2,765826
answered Apr 23 at 12:45
George.PalaciosGeorge.Palacios
2,765826
2,765826
Yes, I noticed that as well (maybe should have said so in my post), but in the link there is mentioned a way to move it (from BOL they say), that is why I got a bit worried. We also have an instance where the two are located in different folders and have been so for years without any problems, but I don't think we have tried upgrading inplace for such a setup. (And that is when the problems will arise according to the link.)
– GHauan
Apr 23 at 13:07
George. Your answer was helpful, but the one from Shanky was a bit more explanatory (if that is a word), so I change the accepted answer to his.
– GHauan
Apr 23 at 14:30
@GHauan absolutely no problem with that - I would suggest in future potentially make your question a bit clearer? IMO I answered the question directly.
– George.Palacios
Apr 23 at 15:00
You are right, my bad. Thank you for taking the time to answer.
– GHauan
yesterday
add a comment |
Yes, I noticed that as well (maybe should have said so in my post), but in the link there is mentioned a way to move it (from BOL they say), that is why I got a bit worried. We also have an instance where the two are located in different folders and have been so for years without any problems, but I don't think we have tried upgrading inplace for such a setup. (And that is when the problems will arise according to the link.)
– GHauan
Apr 23 at 13:07
George. Your answer was helpful, but the one from Shanky was a bit more explanatory (if that is a word), so I change the accepted answer to his.
– GHauan
Apr 23 at 14:30
@GHauan absolutely no problem with that - I would suggest in future potentially make your question a bit clearer? IMO I answered the question directly.
– George.Palacios
Apr 23 at 15:00
You are right, my bad. Thank you for taking the time to answer.
– GHauan
yesterday
Yes, I noticed that as well (maybe should have said so in my post), but in the link there is mentioned a way to move it (from BOL they say), that is why I got a bit worried. We also have an instance where the two are located in different folders and have been so for years without any problems, but I don't think we have tried upgrading inplace for such a setup. (And that is when the problems will arise according to the link.)
– GHauan
Apr 23 at 13:07
Yes, I noticed that as well (maybe should have said so in my post), but in the link there is mentioned a way to move it (from BOL they say), that is why I got a bit worried. We also have an instance where the two are located in different folders and have been so for years without any problems, but I don't think we have tried upgrading inplace for such a setup. (And that is when the problems will arise according to the link.)
– GHauan
Apr 23 at 13:07
George. Your answer was helpful, but the one from Shanky was a bit more explanatory (if that is a word), so I change the accepted answer to his.
– GHauan
Apr 23 at 14:30
George. Your answer was helpful, but the one from Shanky was a bit more explanatory (if that is a word), so I change the accepted answer to his.
– GHauan
Apr 23 at 14:30
@GHauan absolutely no problem with that - I would suggest in future potentially make your question a bit clearer? IMO I answered the question directly.
– George.Palacios
Apr 23 at 15:00
@GHauan absolutely no problem with that - I would suggest in future potentially make your question a bit clearer? IMO I answered the question directly.
– George.Palacios
Apr 23 at 15:00
You are right, my bad. Thank you for taking the time to answer.
– GHauan
yesterday
You are right, my bad. Thank you for taking the time to answer.
– GHauan
yesterday
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%2f235469%2fsql-server-placement-of-master-database-files-vs-resource-database-files%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
