|
|
|
|
||||||
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Hello:
At the beginning of this brand new SQL 2005 install, I am trying to move the data and log files to separate locations. I just need to move the log file of mssqlsystemresource. The data file is fine where it is. I am following that knowledge base article dated September 2007 to the letter. But, when I run the ALTER DATABASE statement, it gives me the message that it cannot find mssqlsystemresource in the sysdatabases entry or something like that. What did I do wrong, and how can I fix? I installed SP2 on there beforehand. SQL Programmer |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
mssqlsystemresource database is a hidden/system database accessed by
DAC. so you wont be able to see mssqlsystemresource using your current or sa credentials. Try out with the DAC and it will work. But here is a pointer, since it is a system database, why dont you leave it at its default location. Mani Singh |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
> But here is a pointer, since it is a system database, why dont you
> leave it at its default location. I agree. I believe that the resource database (both files) *need* to be same path as the master database (mdf file). BOL should have more info. SQL Programmer: You mention "that knowledge base article". If you tell us which it is and where we can find it, we can have a look at it and see if the article need adjustment or if you perhaps misunderstood anything in the article. -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Maninder" <msdhanjal@gmail.com> wrote in message news:fb0e6708-5f0d-45b7-b973-3588bc19a3c7@k37g2000hsf.googlegroups.com... > mssqlsystemresource database is a hidden/system database accessed by > DAC. so you wont be able to see mssqlsystemresource using your current > or sa credentials. Try out with the DAC and it will work. > But here is a pointer, since it is a system database, why dont you > leave it at its default location. > > Mani Singh |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
Hello,
First of all, be aware that mssqlsystemresource mdf,ldf files have to reside at the exact same location as Master database. These are the steps: 1. From a command prompt enter the following command: NET START MSSQLSERVER /f /T3608 2. Run the following script in SQL Server Management Studio (assuming 'R:\MSSQL\DATA\' is where you want to move) : ALTER DATABASE mssqlsystemresource MODIFY FILE (Name=log, FILENAME = 'R:\MSSQL\DATA\mssqlsystemresource.ldf'); GO 3. Stop SQLServer service by right-clicking in Configuration Manager 4. Move 'Mssqlsystemresource.ldf' file from existing location to desired location (R:\MSSQL\Data) 5. From a command prompt enter the following command: NET START MSSQLSERVER /f /T3608 6. Run the following script in SQL Server Management Studio ALTER DATABASE mssqlsystemresource SET READ_ONLY; 7.Stop SQLServer service by right-clicking in Configuration Manager 8. Start SQLServer service by right-clicking in Configuration Manager 9. Verify and confirm changes: SELECT name, physical_name AS CurrentLocation, state_desc FROM sys.master_files WHERE database_id = DB_ID('master'); HTH SQL_ "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in message news:89FC3616-CFAE-4EE0-B3D3-8B982A733450@microsoft.com... > Hello: > > At the beginning of this brand new SQL 2005 install, I am trying to move > the > data and log files to separate locations. > > I just need to move the log file of mssqlsystemresource. The data file is > fine where it is. > > I am following that knowledge base article dated September 2007 to the > letter. But, when I run the ALTER DATABASE statement, it gives me the > message that it cannot find mssqlsystemresource in the sysdatabases entry > or > something like that. > > What did I do wrong, and how can I fix? > > I installed SP2 on there beforehand. > > SQL Programmer |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
Again, when I run the ALTER DATABASE command, it gives me a message saying
that it cannot locate mssqlsystemresource in sysdatabases.... I don't get it. This isn't the first time that I've done this. I don't know what's different this time. SQL Programmer "SQL_" wrote: > Hello, > > First of all, be aware that mssqlsystemresource mdf,ldf files have to reside > at the exact same location as Master database. These are the steps: > > 1. From a command prompt enter the following command: > NET START MSSQLSERVER /f /T3608 > > 2. Run the following script in SQL Server Management Studio (assuming > 'R:\MSSQL\DATA\' is where you want to move) : > > ALTER DATABASE mssqlsystemresource > MODIFY FILE (Name=log, FILENAME = > 'R:\MSSQL\DATA\mssqlsystemresource.ldf'); > GO > > 3. Stop SQLServer service by right-clicking in Configuration Manager > > 4. Move 'Mssqlsystemresource.ldf' file from existing location to desired > location (R:\MSSQL\Data) > > 5. From a command prompt enter the following command: > NET START MSSQLSERVER /f /T3608 > > > 6. Run the following script in SQL Server Management Studio > ALTER DATABASE mssqlsystemresource SET READ_ONLY; > > 7.Stop SQLServer service by right-clicking in Configuration Manager > > 8. Start SQLServer service by right-clicking in Configuration Manager > > 9. Verify and confirm changes: > SELECT name, physical_name AS CurrentLocation, state_desc > FROM sys.master_files > WHERE database_id = DB_ID('master'); > > > HTH > SQL_ > > "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in message > news:89FC3616-CFAE-4EE0-B3D3-8B982A733450@microsoft.com... > > Hello: > > > > At the beginning of this brand new SQL 2005 install, I am trying to move > > the > > data and log files to separate locations. > > > > I just need to move the log file of mssqlsystemresource. The data file is > > fine where it is. > > > > I am following that knowledge base article dated September 2007 to the > > letter. But, when I run the ALTER DATABASE statement, it gives me the > > message that it cannot find mssqlsystemresource in the sysdatabases entry > > or > > something like that. > > > > What did I do wrong, and how can I fix? > > > > I installed SP2 on there beforehand. > > > > SQL Programmer > > > |
|
|
|
#6 |
|
Messages: n/a
Hébergeur: |
I wish that that article had a number or identifier on it. But, it doesn't.
Besides the date, all I can describe is that it is an MSDN article that goes into lengthy detail on moving databases. When I run the ALTER DATABASE command, it gives me a message saying that it cannot locate mssqlsystemresource in sysdatabases.... I don't get it. This isn't the first time that I've done this. I don't know what's different this time. SQL Programmer "Tibor Karaszi" wrote: > > But here is a pointer, since it is a system database, why dont you > > leave it at its default location. > > I agree. I believe that the resource database (both files) *need* to be same path as the master > database (mdf file). BOL should have more info. > > > SQL Programmer: > You mention "that knowledge base article". If you tell us which it is and where we can find it, we > can have a look at it and see if the article need adjustment or if you perhaps misunderstood > anything in the article. > > -- > Tibor Karaszi, SQL Server MVP > http://www.karaszi.com/sqlserver/default.asp > http://sqlblog.com/blogs/tibor_karaszi > > > "Maninder" <msdhanjal@gmail.com> wrote in message > news:fb0e6708-5f0d-45b7-b973-3588bc19a3c7@k37g2000hsf.googlegroups.com... > > mssqlsystemresource database is a hidden/system database accessed by > > DAC. so you wont be able to see mssqlsystemresource using your current > > or sa credentials. Try out with the DAC and it will work. > > But here is a pointer, since it is a system database, why dont you > > leave it at its default location. > > > > Mani Singh > > > |
|
|
|
#7 |
|
Messages: n/a
Hébergeur: |
What's DAC? I'm unclear.
Our firm's best practices dictate moving mdf and ldf files to different locations--even that of system databases. SQL Programmer "Maninder" wrote: > mssqlsystemresource database is a hidden/system database accessed by > DAC. so you wont be able to see mssqlsystemresource using your current > or sa credentials. Try out with the DAC and it will work. > But here is a pointer, since it is a system database, why dont you > leave it at its default location. > > Mani Singh > |
|
|
|
#8 |
|
Messages: n/a
Hébergeur: |
Hi
To move the master database and resource database, follow these steps. Open the SQL Server Configuration Manager. Right-click on the desired instance of SQL Server, choose Properties, and then click on the Advanced tab. Edit the Startup Parameters values to point to the new directory location for the master database data and log files. You can optionally choose to also move the SQL Server error log files. The parameter value for the data file must follow the -d parameter, the value for the log file must follow the -l parameter, and the value for the error log must follow the –e parameter, as shown here: -dE:\SQLData\master.mdf;- eC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG; -lE:\SQLData\mastlog.ldf; -eE:\ SQLData\LOG\ERRORLOG;- Stop the instance of SQL Server and physically move the files for master and mssqlsystemresource to the new location. Start the instance of SQL Server in master-only recovery mode by using the /f and / T3608 flags NET START MSSQLSERVER /f /T3608 Using SQLCMD commands or SQL Server Management Studio, use ALTER DATABASE to change the FILENAME path for the mssqlsystemresource database to match the new location of the master data file. Do not change the name of the database or the file names. ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=data, FILENAME= 'new_path_of_master\mssqlsystemresource.mdf'); ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=log, FILENAME= 'new_path_of_master\mssqlsystemresource.ldf'); Set the mssqlsystemresource database to read-only, and stop the instance of SQL Server. Move the resource database’s data and log files to the new location. Restart the instance of SQL Server. Verify the file change for the master database by running the following query. Note that you cannot view the resource database metadata by using the system catalog views or system tables. SELECT name, physical_name AS CurrentLocation, state_desc FROM sys.master_files WHERE database_id = DB_ID('master'); "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in message news:037CF09D-FCA0-4E66-B3BD-8B008B40BD32@microsoft.com... > Again, when I run the ALTER DATABASE command, it gives me a message saying > that it cannot locate mssqlsystemresource in sysdatabases.... > > I don't get it. This isn't the first time that I've done this. I don't > know what's different this time. > > SQL Programmer > > "SQL_" wrote: > >> Hello, >> >> First of all, be aware that mssqlsystemresource mdf,ldf files have to >> reside >> at the exact same location as Master database. These are the steps: >> >> 1. From a command prompt enter the following command: >> NET START MSSQLSERVER /f /T3608 >> >> 2. Run the following script in SQL Server Management Studio (assuming >> 'R:\MSSQL\DATA\' is where you want to move) : >> >> ALTER DATABASE mssqlsystemresource >> MODIFY FILE (Name=log, FILENAME = >> 'R:\MSSQL\DATA\mssqlsystemresource.ldf'); >> GO >> >> 3. Stop SQLServer service by right-clicking in Configuration Manager >> >> 4. Move 'Mssqlsystemresource.ldf' file from existing location to desired >> location (R:\MSSQL\Data) >> >> 5. From a command prompt enter the following command: >> NET START MSSQLSERVER /f /T3608 >> >> >> 6. Run the following script in SQL Server Management Studio >> ALTER DATABASE mssqlsystemresource SET READ_ONLY; >> >> 7.Stop SQLServer service by right-clicking in Configuration Manager >> >> 8. Start SQLServer service by right-clicking in Configuration Manager >> >> 9. Verify and confirm changes: >> SELECT name, physical_name AS CurrentLocation, state_desc >> FROM sys.master_files >> WHERE database_id = DB_ID('master'); >> >> >> HTH >> SQL_ >> >> "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in >> message >> news:89FC3616-CFAE-4EE0-B3D3-8B982A733450@microsoft.com... >> > Hello: >> > >> > At the beginning of this brand new SQL 2005 install, I am trying to >> > move >> > the >> > data and log files to separate locations. >> > >> > I just need to move the log file of mssqlsystemresource. The data file >> > is >> > fine where it is. >> > >> > I am following that knowledge base article dated September 2007 to the >> > letter. But, when I run the ALTER DATABASE statement, it gives me the >> > message that it cannot find mssqlsystemresource in the sysdatabases >> > entry >> > or >> > something like that. >> > >> > What did I do wrong, and how can I fix? >> > >> > I installed SP2 on there beforehand. >> > >> > SQL Programmer >> >> >> |
|
|
|
#9 |
|
Messages: n/a
Hébergeur: |
I tried all of that.
"Uri Dimant" wrote: > Hi > > To move the master database and resource database, follow these steps. > > Open the SQL Server Configuration Manager. Right-click on the desired > instance of SQL Server, choose Properties, and then click on the Advanced > tab. > > Edit the Startup Parameters values to point to the new directory location > for the master database data and log files. You can optionally choose to > also move the SQL Server error log files. The parameter value for the data > file must follow the -d parameter, the value for the log file must follow > the -l parameter, and the value for the error log must follow the –e > parameter, as shown here: > > -dE:\SQLData\master.mdf;- > eC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG; > -lE:\SQLData\mastlog.ldf; > -eE:\ SQLData\LOG\ERRORLOG;- > Stop the instance of SQL Server and physically move the files for master and > mssqlsystemresource to the new location. > > Start the instance of SQL Server in master-only recovery mode by using the > /f and / T3608 flags > NET START MSSQLSERVER /f /T3608 > > > > Using SQLCMD commands or SQL Server Management Studio, use ALTER DATABASE to > change the FILENAME path for the mssqlsystemresource database to match the > new location of the master data file. Do not change the name of the database > or the file names. > > ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=data, FILENAME= > 'new_path_of_master\mssqlsystemresource.mdf'); > ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=log, FILENAME= > 'new_path_of_master\mssqlsystemresource.ldf'); > Set the mssqlsystemresource database to read-only, and stop the instance of > SQL Server. > > Move the resource database’s data and log files to the new location. > > Restart the instance of SQL Server. > > Verify the file change for the master database by running the following > query. Note that you cannot view the resource database metadata by using the > system catalog views or system tables. > > SELECT name, physical_name AS CurrentLocation, state_desc > FROM sys.master_files > WHERE database_id = DB_ID('master'); > > > > > "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in message > news:037CF09D-FCA0-4E66-B3BD-8B008B40BD32@microsoft.com... > > Again, when I run the ALTER DATABASE command, it gives me a message saying > > that it cannot locate mssqlsystemresource in sysdatabases.... > > > > I don't get it. This isn't the first time that I've done this. I don't > > know what's different this time. > > > > SQL Programmer > > > > "SQL_" wrote: > > > >> Hello, > >> > >> First of all, be aware that mssqlsystemresource mdf,ldf files have to > >> reside > >> at the exact same location as Master database. These are the steps: > >> > >> 1. From a command prompt enter the following command: > >> NET START MSSQLSERVER /f /T3608 > >> > >> 2. Run the following script in SQL Server Management Studio (assuming > >> 'R:\MSSQL\DATA\' is where you want to move) : > >> > >> ALTER DATABASE mssqlsystemresource > >> MODIFY FILE (Name=log, FILENAME = > >> 'R:\MSSQL\DATA\mssqlsystemresource.ldf'); > >> GO > >> > >> 3. Stop SQLServer service by right-clicking in Configuration Manager > >> > >> 4. Move 'Mssqlsystemresource.ldf' file from existing location to desired > >> location (R:\MSSQL\Data) > >> > >> 5. From a command prompt enter the following command: > >> NET START MSSQLSERVER /f /T3608 > >> > >> > >> 6. Run the following script in SQL Server Management Studio > >> ALTER DATABASE mssqlsystemresource SET READ_ONLY; > >> > >> 7.Stop SQLServer service by right-clicking in Configuration Manager > >> > >> 8. Start SQLServer service by right-clicking in Configuration Manager > >> > >> 9. Verify and confirm changes: > >> SELECT name, physical_name AS CurrentLocation, state_desc > >> FROM sys.master_files > >> WHERE database_id = DB_ID('master'); > >> > >> > >> HTH > >> SQL_ > >> > >> "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in > >> message > >> news:89FC3616-CFAE-4EE0-B3D3-8B982A733450@microsoft.com... > >> > Hello: > >> > > >> > At the beginning of this brand new SQL 2005 install, I am trying to > >> > move > >> > the > >> > data and log files to separate locations. > >> > > >> > I just need to move the log file of mssqlsystemresource. The data file > >> > is > >> > fine where it is. > >> > > >> > I am following that knowledge base article dated September 2007 to the > >> > letter. But, when I run the ALTER DATABASE statement, it gives me the > >> > message that it cannot find mssqlsystemresource in the sysdatabases > >> > entry > >> > or > >> > something like that. > >> > > >> > What did I do wrong, and how can I fix? > >> > > >> > I installed SP2 on there beforehand. > >> > > >> > SQL Programmer > >> > >> > >> > > > |
|
|
|
#10 |
|
Messages: n/a
Hébergeur: |
Hi
Ok, now , do not look at the document , describe please step by step what you did , in order to reproduce on my machine the same error. "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in message news:B2E48336-655C-4B54-B5D2-A8118F711DFB@microsoft.com... >I tried all of that. > > "Uri Dimant" wrote: > >> Hi >> >> To move the master database and resource database, follow these steps. >> >> Open the SQL Server Configuration Manager. Right-click on the desired >> instance of SQL Server, choose Properties, and then click on the Advanced >> tab. >> >> Edit the Startup Parameters values to point to the new directory location >> for the master database data and log files. You can optionally choose to >> also move the SQL Server error log files. The parameter value for the >> data >> file must follow the -d parameter, the value for the log file must follow >> the -l parameter, and the value for the error log must follow the –e >> parameter, as shown here: >> >> -dE:\SQLData\master.mdf;- >> eC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG; >> -lE:\SQLData\mastlog.ldf; >> -eE:\ SQLData\LOG\ERRORLOG;- >> Stop the instance of SQL Server and physically move the files for master >> and >> mssqlsystemresource to the new location. >> >> Start the instance of SQL Server in master-only recovery mode by using >> the >> /f and / T3608 flags >> NET START MSSQLSERVER /f /T3608 >> >> >> >> Using SQLCMD commands or SQL Server Management Studio, use ALTER DATABASE >> to >> change the FILENAME path for the mssqlsystemresource database to match >> the >> new location of the master data file. Do not change the name of the >> database >> or the file names. >> >> ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=data, FILENAME= >> 'new_path_of_master\mssqlsystemresource.mdf'); >> ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=log, FILENAME= >> 'new_path_of_master\mssqlsystemresource.ldf'); >> Set the mssqlsystemresource database to read-only, and stop the instance >> of >> SQL Server. >> >> Move the resource database’s data and log files to the new location. >> >> Restart the instance of SQL Server. >> >> Verify the file change for the master database by running the following >> query. Note that you cannot view the resource database metadata by using >> the >> system catalog views or system tables. >> >> SELECT name, physical_name AS CurrentLocation, state_desc >> FROM sys.master_files >> WHERE database_id = DB_ID('master'); >> >> >> >> >> "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in >> message >> news:037CF09D-FCA0-4E66-B3BD-8B008B40BD32@microsoft.com... >> > Again, when I run the ALTER DATABASE command, it gives me a message >> > saying >> > that it cannot locate mssqlsystemresource in sysdatabases.... >> > >> > I don't get it. This isn't the first time that I've done this. I >> > don't >> > know what's different this time. >> > >> > SQL Programmer >> > >> > "SQL_" wrote: >> > >> >> Hello, >> >> >> >> First of all, be aware that mssqlsystemresource mdf,ldf files have to >> >> reside >> >> at the exact same location as Master database. These are the steps: >> >> >> >> 1. From a command prompt enter the following command: >> >> NET START MSSQLSERVER /f /T3608 >> >> >> >> 2. Run the following script in SQL Server Management Studio (assuming >> >> 'R:\MSSQL\DATA\' is where you want to move) : >> >> >> >> ALTER DATABASE mssqlsystemresource >> >> MODIFY FILE (Name=log, FILENAME = >> >> 'R:\MSSQL\DATA\mssqlsystemresource.ldf'); >> >> GO >> >> >> >> 3. Stop SQLServer service by right-clicking in Configuration Manager >> >> >> >> 4. Move 'Mssqlsystemresource.ldf' file from existing location to >> >> desired >> >> location (R:\MSSQL\Data) >> >> >> >> 5. From a command prompt enter the following command: >> >> NET START MSSQLSERVER /f /T3608 >> >> >> >> >> >> 6. Run the following script in SQL Server Management Studio >> >> ALTER DATABASE mssqlsystemresource SET READ_ONLY; >> >> >> >> 7.Stop SQLServer service by right-clicking in Configuration Manager >> >> >> >> 8. Start SQLServer service by right-clicking in Configuration Manager >> >> >> >> 9. Verify and confirm changes: >> >> SELECT name, physical_name AS CurrentLocation, state_desc >> >> FROM sys.master_files >> >> WHERE database_id = DB_ID('master'); >> >> >> >> >> >> HTH >> >> SQL_ >> >> >> >> "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in >> >> message >> >> news:89FC3616-CFAE-4EE0-B3D3-8B982A733450@microsoft.com... >> >> > Hello: >> >> > >> >> > At the beginning of this brand new SQL 2005 install, I am trying to >> >> > move >> >> > the >> >> > data and log files to separate locations. >> >> > >> >> > I just need to move the log file of mssqlsystemresource. The data >> >> > file >> >> > is >> >> > fine where it is. >> >> > >> >> > I am following that knowledge base article dated September 2007 to >> >> > the >> >> > letter. But, when I run the ALTER DATABASE statement, it gives me >> >> > the >> >> > message that it cannot find mssqlsystemresource in the sysdatabases >> >> > entry >> >> > or >> >> > something like that. >> >> > >> >> > What did I do wrong, and how can I fix? >> >> > >> >> > I installed SP2 on there beforehand. >> >> > >> >> > SQL Programmer >> >> >> >> >> >> >> >> >> |
|
|
|
#11 |
|
Messages: n/a
Hébergeur: |
OK. I started the steps over again, since I did not know what else to do. I
ran through Configuration and changed the log pathing. (It's only the mastlog and likewise the mssqlsystemresource log that I want to move.) When I went to either sqlcmd or "Query Analyzer" to run the ALTER DATABASE commmand, I would get that crappy only one admin can login at this time. ot, in sqlcmd, I would get the "this database must be in a writable state". I don't know what the hell else to do other than uninstalling and reinstalling. SQL 2005 is lousy technology. "Uri Dimant" wrote: > Hi > Ok, now , do not look at the document , describe please step by step what > you did , in order to reproduce on my machine the same error. > > > > > > "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in message > news:B2E48336-655C-4B54-B5D2-A8118F711DFB@microsoft.com... > >I tried all of that. > > > > "Uri Dimant" wrote: > > > >> Hi > >> > >> To move the master database and resource database, follow these steps. > >> > >> Open the SQL Server Configuration Manager. Right-click on the desired > >> instance of SQL Server, choose Properties, and then click on the Advanced > >> tab. > >> > >> Edit the Startup Parameters values to point to the new directory location > >> for the master database data and log files. You can optionally choose to > >> also move the SQL Server error log files. The parameter value for the > >> data > >> file must follow the -d parameter, the value for the log file must follow > >> the -l parameter, and the value for the error log must follow the –e > >> parameter, as shown here: > >> > >> -dE:\SQLData\master.mdf;- > >> eC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG; > >> -lE:\SQLData\mastlog.ldf; > >> -eE:\ SQLData\LOG\ERRORLOG;- > >> Stop the instance of SQL Server and physically move the files for master > >> and > >> mssqlsystemresource to the new location. > >> > >> Start the instance of SQL Server in master-only recovery mode by using > >> the > >> /f and / T3608 flags > >> NET START MSSQLSERVER /f /T3608 > >> > >> > >> > >> Using SQLCMD commands or SQL Server Management Studio, use ALTER DATABASE > >> to > >> change the FILENAME path for the mssqlsystemresource database to match > >> the > >> new location of the master data file. Do not change the name of the > >> database > >> or the file names. > >> > >> ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=data, FILENAME= > >> 'new_path_of_master\mssqlsystemresource.mdf'); > >> ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=log, FILENAME= > >> 'new_path_of_master\mssqlsystemresource.ldf'); > >> Set the mssqlsystemresource database to read-only, and stop the instance > >> of > >> SQL Server. > >> > >> Move the resource database’s data and log files to the new location. > >> > >> Restart the instance of SQL Server. > >> > >> Verify the file change for the master database by running the following > >> query. Note that you cannot view the resource database metadata by using > >> the > >> system catalog views or system tables. > >> > >> SELECT name, physical_name AS CurrentLocation, state_desc > >> FROM sys.master_files > >> WHERE database_id = DB_ID('master'); > >> > >> > >> > >> > >> "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in > >> message > >> news:037CF09D-FCA0-4E66-B3BD-8B008B40BD32@microsoft.com... > >> > Again, when I run the ALTER DATABASE command, it gives me a message > >> > saying > >> > that it cannot locate mssqlsystemresource in sysdatabases.... > >> > > >> > I don't get it. This isn't the first time that I've done this. I > >> > don't > >> > know what's different this time. > >> > > >> > SQL Programmer > >> > > >> > "SQL_" wrote: > >> > > >> >> Hello, > >> >> > >> >> First of all, be aware that mssqlsystemresource mdf,ldf files have to > >> >> reside > >> >> at the exact same location as Master database. These are the steps: > >> >> > >> >> 1. From a command prompt enter the following command: > >> >> NET START MSSQLSERVER /f /T3608 > >> >> > >> >> 2. Run the following script in SQL Server Management Studio (assuming > >> >> 'R:\MSSQL\DATA\' is where you want to move) : > >> >> > >> >> ALTER DATABASE mssqlsystemresource > >> >> MODIFY FILE (Name=log, FILENAME = > >> >> 'R:\MSSQL\DATA\mssqlsystemresource.ldf'); > >> >> GO > >> >> > >> >> 3. Stop SQLServer service by right-clicking in Configuration Manager > >> >> > >> >> 4. Move 'Mssqlsystemresource.ldf' file from existing location to > >> >> desired > >> >> location (R:\MSSQL\Data) > >> >> > >> >> 5. From a command prompt enter the following command: > >> >> NET START MSSQLSERVER /f /T3608 > >> >> > >> >> > >> >> 6. Run the following script in SQL Server Management Studio > >> >> ALTER DATABASE mssqlsystemresource SET READ_ONLY; > >> >> > >> >> 7.Stop SQLServer service by right-clicking in Configuration Manager > >> >> > >> >> 8. Start SQLServer service by right-clicking in Configuration Manager > >> >> > >> >> 9. Verify and confirm changes: > >> >> SELECT name, physical_name AS CurrentLocation, state_desc > >> >> FROM sys.master_files > >> >> WHERE database_id = DB_ID('master'); > >> >> > >> >> > >> >> HTH > >> >> SQL_ > >> >> > >> >> "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in > >> >> message > >> >> news:89FC3616-CFAE-4EE0-B3D3-8B982A733450@microsoft.com... > >> >> > Hello: > >> >> > > >> >> > At the beginning of this brand new SQL 2005 install, I am trying to > >> >> > move > >> >> > the > >> >> > data and log files to separate locations. > >> >> > > >> >> > I just need to move the log file of mssqlsystemresource. The data > >> >> > file > >> >> > is > >> >> > fine where it is. > >> >> > > >> >> > I am following that knowledge base article dated September 2007 to > >> >> > the > >> >> > letter. But, when I run the ALTER DATABASE statement, it gives me > >> >> > the > >> >> > message that it cannot find mssqlsystemresource in the sysdatabases > >> >> > entry > >> >> > or > >> >> > something like that. > >> >> > > >> >> > What did I do wrong, and how can I fix? > >> >> > > >> >> > I installed SP2 on there beforehand. > >> >> > > >> >> > SQL Programmer > >> >> > >> >> > >> >> > >> > >> > >> > > > |
|
|
|
#12 |
|
Messages: n/a
Hébergeur: |
Hi
And you put the server with single user mode , then stop and restart. Specify also path for datafiles as wee and see what is going on > I don't know what the hell else to do other than uninstalling and > reinstalling. SQL 2005 is lousy technology. Look, if things go so bad , re-install SQL Server is also an option. Do not forget script out jobs ,alerts and backup database "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in message news:196CF5D0-8A8A-48F9-A8CC-FBF047EC9FA0@microsoft.com... > OK. I started the steps over again, since I did not know what else to do. > I > ran through Configuration and changed the log pathing. (It's only the > mastlog and likewise the mssqlsystemresource log that I want to move.) > > When I went to either sqlcmd or "Query Analyzer" to run the ALTER DATABASE > commmand, I would get that crappy only one admin can login at this time. > ot, > in sqlcmd, I would get the "this database must be in a writable state". > > I don't know what the hell else to do other than uninstalling and > reinstalling. SQL 2005 is lousy technology. > > "Uri Dimant" wrote: > >> Hi >> Ok, now , do not look at the document , describe please step by step what >> you did , in order to reproduce on my machine the same error. >> >> >> >> >> >> "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in >> message >> news:B2E48336-655C-4B54-B5D2-A8118F711DFB@microsoft.com... >> >I tried all of that. >> > >> > "Uri Dimant" wrote: >> > >> >> Hi >> >> >> >> To move the master database and resource database, follow these steps. >> >> >> >> Open the SQL Server Configuration Manager. Right-click on the desired >> >> instance of SQL Server, choose Properties, and then click on the >> >> Advanced >> >> tab. >> >> >> >> Edit the Startup Parameters values to point to the new directory >> >> location >> >> for the master database data and log files. You can optionally choose >> >> to >> >> also move the SQL Server error log files. The parameter value for the >> >> data >> >> file must follow the -d parameter, the value for the log file must >> >> follow >> >> the -l parameter, and the value for the error log must follow the –e >> >> parameter, as shown here: >> >> >> >> -dE:\SQLData\master.mdf;- >> >> eC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG; >> >> -lE:\SQLData\mastlog.ldf; >> >> -eE:\ SQLData\LOG\ERRORLOG;- >> >> Stop the instance of SQL Server and physically move the files for >> >> master >> >> and >> >> mssqlsystemresource to the new location. >> >> >> >> Start the instance of SQL Server in master-only recovery mode by using >> >> the >> >> /f and / T3608 flags >> >> NET START MSSQLSERVER /f /T3608 >> >> >> >> >> >> >> >> Using SQLCMD commands or SQL Server Management Studio, use ALTER >> >> DATABASE >> >> to >> >> change the FILENAME path for the mssqlsystemresource database to match >> >> the >> >> new location of the master data file. Do not change the name of the >> >> database >> >> or the file names. >> >> >> >> ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=data, FILENAME= >> >> 'new_path_of_master\mssqlsystemresource.mdf'); >> >> ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=log, FILENAME= >> >> 'new_path_of_master\mssqlsystemresource.ldf'); >> >> Set the mssqlsystemresource database to read-only, and stop the >> >> instance >> >> of >> >> SQL Server. >> >> >> >> Move the resource database’s data and log files to the new location. >> >> >> >> Restart the instance of SQL Server. >> >> >> >> Verify the file change for the master database by running the >> >> following >> >> query. Note that you cannot view the resource database metadata by >> >> using >> >> the >> >> system catalog views or system tables. >> >> >> >> SELECT name, physical_name AS CurrentLocation, state_desc >> >> FROM sys.master_files >> >> WHERE database_id = DB_ID('master'); >> >> >> >> >> >> >> >> >> >> "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in >> >> message >> >> news:037CF09D-FCA0-4E66-B3BD-8B008B40BD32@microsoft.com... >> >> > Again, when I run the ALTER DATABASE command, it gives me a message >> >> > saying >> >> > that it cannot locate mssqlsystemresource in sysdatabases.... >> >> > >> >> > I don't get it. This isn't the first time that I've done this. I >> >> > don't >> >> > know what's different this time. >> >> > >> >> > SQL Programmer >> >> > >> >> > "SQL_" wrote: >> >> > >> >> >> Hello, >> >> >> >> >> >> First of all, be aware that mssqlsystemresource mdf,ldf files have >> >> >> to >> >> >> reside >> >> >> at the exact same location as Master database. These are the steps: >> >> >> >> >> >> 1. From a command prompt enter the following command: >> >> >> NET START MSSQLSERVER /f /T3608 >> >> >> >> >> >> 2. Run the following script in SQL Server Management Studio >> >> >> (assuming >> >> >> 'R:\MSSQL\DATA\' is where you want to move) : >> >> >> >> >> >> ALTER DATABASE mssqlsystemresource >> >> >> MODIFY FILE (Name=log, FILENAME = >> >> >> 'R:\MSSQL\DATA\mssqlsystemresource.ldf'); >> >> >> GO >> >> >> >> >> >> 3. Stop SQLServer service by right-clicking in Configuration >> >> >> Manager >> >> >> >> >> >> 4. Move 'Mssqlsystemresource.ldf' file from existing location to >> >> >> desired >> >> >> location (R:\MSSQL\Data) >> >> >> >> >> >> 5. From a command prompt enter the following command: >> >> >> NET START MSSQLSERVER /f /T3608 >> >> >> >> >> >> >> >> >> 6. Run the following script in SQL Server Management Studio >> >> >> ALTER DATABASE mssqlsystemresource SET READ_ONLY; >> >> >> >> >> >> 7.Stop SQLServer service by right-clicking in Configuration Manager >> >> >> >> >> >> 8. Start SQLServer service by right-clicking in Configuration >> >> >> Manager >> >> >> >> >> >> 9. Verify and confirm changes: >> >> >> SELECT name, physical_name AS CurrentLocation, state_desc >> >> >> FROM sys.master_files >> >> >> WHERE database_id = DB_ID('master'); >> >> >> >> >> >> >> >> >> HTH >> >> >> SQL_ >> >> >> >> >> >> "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in >> >> >> message >> >> >> news:89FC3616-CFAE-4EE0-B3D3-8B982A733450@microsoft.com... >> >> >> > Hello: >> >> >> > >> >> >> > At the beginning of this brand new SQL 2005 install, I am trying >> >> >> > to >> >> >> > move >> >> >> > the >> >> >> > data and log files to separate locations. >> >> >> > >> >> >> > I just need to move the log file of mssqlsystemresource. The >> >> >> > data >> >> >> > file >> >> >> > is >> >> >> > fine where it is. >> >> >> > >> >> >> > I am following that knowledge base article dated September 2007 >> >> >> > to >> >> >> > the >> >> >> > letter. But, when I run the ALTER DATABASE statement, it gives >> >> >> > me >> >> >> > the >> >> >> > message that it cannot find mssqlsystemresource in the >> >> >> > sysdatabases >> >> >> > entry >> >> >> > or >> >> >> > something like that. >> >> >> > >> >> >> > What did I do wrong, and how can I fix? >> >> >> > >> >> >> > I installed SP2 on there beforehand. >> >> >> > >> >> >> > SQL Programmer >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> |
|
|
|
#13 |
|
Messages: n/a
Hébergeur: |
I apologize for my demeanor and what i said about SQL 2005. My life has been
one big joke and lack of job credibility is the last thing that I need. Thanks, for your ! I'm uninstalling, now. "Uri Dimant" wrote: > Hi > And you put the server with single user mode , then stop and restart. > Specify also path for datafiles as wee and see what is going on > > > I don't know what the hell else to do other than uninstalling and > > reinstalling. SQL 2005 is lousy technology. > > Look, if things go so bad , re-install SQL Server is also an option. Do not > forget script out jobs ,alerts and backup database > > > > > "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in message > news:196CF5D0-8A8A-48F9-A8CC-FBF047EC9FA0@microsoft.com... > > OK. I started the steps over again, since I did not know what else to do. > > I > > ran through Configuration and changed the log pathing. (It's only the > > mastlog and likewise the mssqlsystemresource log that I want to move.) > > > > When I went to either sqlcmd or "Query Analyzer" to run the ALTER DATABASE > > commmand, I would get that crappy only one admin can login at this time. > > ot, > > in sqlcmd, I would get the "this database must be in a writable state". > > > > I don't know what the hell else to do other than uninstalling and > > reinstalling. SQL 2005 is lousy technology. > > > > "Uri Dimant" wrote: > > > >> Hi > >> Ok, now , do not look at the document , describe please step by step what > >> you did , in order to reproduce on my machine the same error. > >> > >> > >> > >> > >> > >> "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in > >> message > >> news:B2E48336-655C-4B54-B5D2-A8118F711DFB@microsoft.com... > >> >I tried all of that. > >> > > >> > "Uri Dimant" wrote: > >> > > >> >> Hi > >> >> > >> >> To move the master database and resource database, follow these steps. > >> >> > >> >> Open the SQL Server Configuration Manager. Right-click on the desired > >> >> instance of SQL Server, choose Properties, and then click on the > >> >> Advanced > >> >> tab. > >> >> > >> >> Edit the Startup Parameters values to point to the new directory > >> >> location > >> >> for the master database data and log files. You can optionally choose > >> >> to > >> >> also move the SQL Server error log files. The parameter value for the > >> >> data > >> >> file must follow the -d parameter, the value for the log file must > >> >> follow > >> >> the -l parameter, and the value for the error log must follow the –e > >> >> parameter, as shown here: > >> >> > >> >> -dE:\SQLData\master.mdf;- > >> >> eC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG; > >> >> -lE:\SQLData\mastlog.ldf; > >> >> -eE:\ SQLData\LOG\ERRORLOG;- > >> >> Stop the instance of SQL Server and physically move the files for > >> >> master > >> >> and > >> >> mssqlsystemresource to the new location. > >> >> > >> >> Start the instance of SQL Server in master-only recovery mode by using > >> >> the > >> >> /f and / T3608 flags > >> >> NET START MSSQLSERVER /f /T3608 > >> >> > >> >> > >> >> > >> >> Using SQLCMD commands or SQL Server Management Studio, use ALTER > >> >> DATABASE > >> >> to > >> >> change the FILENAME path for the mssqlsystemresource database to match > >> >> the > >> >> new location of the master data file. Do not change the name of the > >> >> database > >> >> or the file names. > >> >> > >> >> ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=data, FILENAME= > >> >> 'new_path_of_master\mssqlsystemresource.mdf'); > >> >> ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=log, FILENAME= > >> >> 'new_path_of_master\mssqlsystemresource.ldf'); > >> >> Set the mssqlsystemresource database to read-only, and stop the > >> >> instance > >> >> of > >> >> SQL Server. > >> >> > >> >> Move the resource database’s data and log files to the new location. > >> >> > >> >> Restart the instance of SQL Server. > >> >> > >> >> Verify the file change for the master database by running the > >> >> following > >> >> query. Note that you cannot view the resource database metadata by > >> >> using > >> >> the > >> >> system catalog views or system tables. > >> >> > >> >> SELECT name, physical_name AS CurrentLocation, state_desc > >> >> FROM sys.master_files > >> >> WHERE database_id = DB_ID('master'); > >> >> > >> >> > >> >> > >> >> > >> >> "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in > >> >> message > >> >> news:037CF09D-FCA0-4E66-B3BD-8B008B40BD32@microsoft.com... > >> >> > Again, when I run the ALTER DATABASE command, it gives me a message > >> >> > saying > >> >> > that it cannot locate mssqlsystemresource in sysdatabases.... > >> >> > > >> >> > I don't get it. This isn't the first time that I've done this. I > >> >> > don't > >> >> > know what's different this time. > >> >> > > >> >> > SQL Programmer > >> >> > > >> >> > "SQL_" wrote: > >> >> > > >> >> >> Hello, > >> >> >> > >> >> >> First of all, be aware that mssqlsystemresource mdf,ldf files have > >> >> >> to > >> >> >> reside > >> >> >> at the exact same location as Master database. These are the steps: > >> >> >> > >> >> >> 1. From a command prompt enter the following command: > >> >> >> NET START MSSQLSERVER /f /T3608 > >> >> >> > >> >> >> 2. Run the following script in SQL Server Management Studio > >> >> >> (assuming > >> >> >> 'R:\MSSQL\DATA\' is where you want to move) : > >> >> >> > >> >> >> ALTER DATABASE mssqlsystemresource > >> >> >> MODIFY FILE (Name=log, FILENAME = > >> >> >> 'R:\MSSQL\DATA\mssqlsystemresource.ldf'); > >> >> >> GO > >> >> >> > >> >> >> 3. Stop SQLServer service by right-clicking in Configuration > >> >> >> Manager > >> >> >> > >> >> >> 4. Move 'Mssqlsystemresource.ldf' file from existing location to > >> >> >> desired > >> >> >> location (R:\MSSQL\Data) > >> >> >> > >> >> >> 5. From a command prompt enter the following command: > >> >> >> NET START MSSQLSERVER /f /T3608 > >> >> >> > >> >> >> > >> >> >> 6. Run the following script in SQL Server Management Studio > >> >> >> ALTER DATABASE mssqlsystemresource SET READ_ONLY; > >> >> >> > >> >> >> 7.Stop SQLServer service by right-clicking in Configuration Manager > >> >> >> > >> >> >> 8. Start SQLServer service by right-clicking in Configuration > >> >> >> Manager > >> >> >> > >> >> >> 9. Verify and confirm changes: > >> >> >> SELECT name, physical_name AS CurrentLocation, state_desc > >> >> >> FROM sys.master_files > >> >> >> WHERE database_id = DB_ID('master'); > >> >> >> > >> >> >> > >> >> >> HTH > >> >> >> SQL_ > >> >> >> > >> >> >> "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in > >> >> >> message > >> >> >> news:89FC3616-CFAE-4EE0-B3D3-8B982A733450@microsoft.com... > >> >> >> > Hello: > >> >> >> > > >> >> >> > At the beginning of this brand new SQL 2005 install, I am trying > >> >> >> > to > >> >> >> > move > >> >> >> > the > >> >> >> > data and log files to separate locations. > >> >> >> > > >> >> >> > I just need to move the log file of mssqlsystemresource. The > >> >> >> > data > >> >> >> > file > >> >> >> > is > >> >> >> > fine where it is. > >> >> >> > > >> >> >> > I am following that knowledge base article dated September 2007 > >> >> >> > to > >> >> >> > the > >> >> >> > letter. But, when I run the ALTER DATABASE statement, it gives > >> >> >> > me > >> >> >> > the > >> >> >> > message that it cannot find mssqlsystemresource in the > >> >> >> > sysdatabases > >> >> >> > entry > >> >> >> > or > >> >> >> > something like that. > >> >> >> > > >> >> >> > What did I do wrong, and how can I fix? > >> >> >> > > >> >> >> > I installed SP2 on there beforehand. > >> >> >> > > >> >> >> > SQL Programmer > >> >> >> > >> >> >> > >> >> >> > >> >> > >> >> > >> >> > >> > >> > >> > > > |
|
|
|
#14 |
|
Messages: n/a
Hébergeur: |
Look resourcedatabase hardly grows and its not visible, so maybe
leaving it in its default Location will . Yes you can surely move other visible system databases. I am not sure and have not tried, what will get hurt as the resource database contains all the system objects. best practise will be to move the tempdb or msdb (in terms of system Databases) if required and leave all other Db's at its default location. Is this best practise made keeping in mind for SQL Server 2005 or was it never revised. Take control as a DBA, and have the power to say no, other than following commands... Make them understand what is possible and what is not... Like you do with security. Rest its up to, how you want to approach it... Pointer: Trying too much to achive nothing is worthless.. yes if it were a VLDB, then it would have made sense to put your act into work.. and trying out all these things... resourcedatabase is a troubleless DB, and rather follow Microsoft Best practise.. or/and talk to a SQL Server MVP. !! DON'T try anything on your PRODUCTION Servers.... |
|
|
|
#15 |
|
Messages: n/a
Hébergeur: |
> OK. I started the steps over again, since I did not know what else to do. > I > ran through Configuration and changed the log pathing. (It's only the > mastlog and likewise the mssqlsystemresource log that I want to move.) Okay, that's the critical piece of information. The resource data and log files need to be in the same location as the master.data file. This is documented in the Books Online topic: http://msdn.microsoft.com/en-us/library/ms345408.aspx where it states "If you move the master database, you must also move the Resource database to the same location as the master data file." In terms of best practices, while it can make sense to separate the data and log files of user databases and tempdb, there really is no point in separating the master or resource data and log files. They just don't get the kind of activity that user dbs and tempdb do. -- Gail Erickson [MS] SQL Server Documentation Team This posting is provided "AS IS" with no warranties, and confers no rights Download the latest version of Books Online from http://technet.microsoft.com/en-us/s.../bb428874.aspx "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in message news:196CF5D0-8A8A-48F9-A8CC-FBF047EC9FA0@microsoft.com... > OK. I started the steps over again, since I did not know what else to do. > I > ran through Configuration and changed the log pathing. (It's only the > mastlog and likewise the mssqlsystemresource log that I want to move.) > > When I went to either sqlcmd or "Query Analyzer" to run the ALTER DATABASE > commmand, I would get that crappy only one admin can login at this time. > ot, > in sqlcmd, I would get the "this database must be in a writable state". > > I don't know what the hell else to do other than uninstalling and > reinstalling. SQL 2005 is lousy technology. > > "Uri Dimant" wrote: > >> Hi >> Ok, now , do not look at the document , describe please step by step what >> you did , in order to reproduce on my machine the same error. >> >> >> >> >> >> "SQL Programmer" <SQLProgrammer@discussions.microsoft.com> wrote in >> message >> news:B2E48336-655C-4B54-B5D2-A8118F711DFB@microsoft.com... >> >I tried all of that. >> > >> > "Uri Dimant" wrote: >> > >> >> Hi >> >> >> >> To move the master database and resource database, follow these steps. >> >> >> >> Open the SQL Server Configuration Manager. Right-click on the desired >> >> instance of SQL Server, choose Properties, and then click on the >> >> Advanced >> >> tab. >> >> >> >> Edit the Startup Parameters values to point to the new directory >> >> location >> >> for the master database data and log files. You can optionally choose >> >> to >> >> also move the SQL Server error log files. The parameter value for the >> >> data >> >> file must follow the -d parameter, the value for the log file must >> >> follow >> >> the -l parameter, and the value for the error log must follow the -e >> >> parameter, as shown here: >> >> >> >> -dE:\SQLData\master.mdf;- >> >> eC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG; >> >> -lE:\SQLData\mastlog.ldf; >> >> -eE:\ SQLData\LOG\ERRORLOG;- >> >> Stop the instance of SQL Server and physically move the files for >> >> master >> >> and >> >> mssqlsystemresource to the new location. >> >> >> >> Start the instance of SQL Server in master-only recovery mode by using >> >> the >> >> /f and / T3608 flags >> >> NET START MSSQLSERVER /f /T3608 >> >> >> >> >> >> >> >> Using SQLCMD commands or SQL Server Management Studio, use ALTER >> >> DATABASE >> >> to >> >> change the FILENAME path for the mssqlsystemresource database to match >> >> the |