November 23, 2009 at 1:23 pm
Can someone help me to move my system db from c drive to e drive. Thank you
November 23, 2009 at 1:35 pm
All system db's or a specific one?
November 23, 2009 at 1:36 pm
all
November 23, 2009 at 1:38 pm
System DB's
http://msdn.microsoft.com/en-us/library/ms345408.aspx
User DB's
http://support.microsoft.com/kb/224071
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 23, 2009 at 11:44 pm
hello,
url was very useful.Thanks.
one more i know is that suppose a new hard or cd drive in place in the system and your database drive letter changes then in sql server surface area configuration system you need make changes in the startup parameters option.
November 23, 2009 at 11:48 pm
oops my bad...
url itself the details i was saying about.. sorry..
November 24, 2009 at 12:38 pm
I moved,but when I am trying to start running instanse I get an error message:The request failed or the service did not respond in timely fashion.Consult the even log. please help me asap. Thank you
November 24, 2009 at 12:44 pm
Go to the Error Log located in MSSQL.X\MSSQL\LOG
look for the file named ErrorLog (without any extension)
See what's mentioned there and post it here if possible..
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 24, 2009 at 12:57 pm
access denied, and we have permissions to everyone now
November 24, 2009 at 12:59 pm
2009-11-24 14:10:19.25 Server (c) 2005 Microsoft Corporation.
2009-11-24 14:10:19.25 Server All rights reserved.
2009-11-24 14:10:19.25 Server Server process ID is 2128.
2009-11-24 14:10:19.25 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\LOG\ERRORLOG'.
2009-11-24 14:10:19.25 Server This instance of SQL Server last reported using a process ID of 6888 at 11/24/2009 2:10:00 PM (local) 11/24/2009 7:10:00 PM (UTC). This is an informational message only; no user action is required.
2009-11-24 14:10:19.25 Server Registry startup parameters:
2009-11-24 14:10:19.25 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\DATA\master.mdf
2009-11-24 14:10:19.25 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\LOG\ERRORLOG
2009-11-24 14:10:19.25 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\DATA\mastlog.ldf
2009-11-24 14:10:19.27 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-11-24 14:10:19.27 Server Detected 1 CPUs. This is an informational message; no user action is required.
2009-11-24 14:10:19.41 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2009-11-24 14:10:19.41 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-11-24 14:10:20.43 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-11-24 14:10:20.43 Server Database Mirroring Transport is disabled in the endpoint configuration.
2009-11-24 14:10:20.43 spid5s Starting up database 'master'.
2009-11-24 14:10:20.60 spid5s CHECKDB for database 'master' finished without errors on 2009-11-23 22:13:35.643 (local time). This is an informational message only; no user action is required.
2009-11-24 14:10:20.63 spid5s SQL Trace ID 1 was started by login "sa".
2009-11-24 14:10:20.66 spid5s Starting up database 'mssqlsystemresource'.
2009-11-24 14:10:20.80 spid5s Server name is 'DEV-SVSQL\INT_OLP'. This is an informational message only. No user action is required.
2009-11-24 14:10:21.00 Server A self-generated certificate was successfully loaded for encryption.
2009-11-24 14:10:21.00 Server Server is listening on [ 'any' <ipv4> 2553].
2009-11-24 14:10:21.00 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\INT_OLP ].
2009-11-24 14:10:21.00 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$INT_OLP\sql\query ].
2009-11-24 14:10:21.00 spid9s Starting up database 'model'.
2009-11-24 14:10:21.00 Server Server is listening on [ 127.0.0.1 <ipv4> 1554].
2009-11-24 14:10:21.00 Server Dedicated admin connection support was established for listening locally on port 1554.
2009-11-24 14:10:21.00 spid9s Error: 17207, Severity: 16, State: 1.
2009-11-24 14:10:21.00 spid9s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'E:\MSSQL\MSSQL.4\MSSQL\Data'. Diagnose and correct the operating system error, and retry the operation.
2009-11-24 14:10:21.02 spid9s Error: 17204, Severity: 16, State: 1.
2009-11-24 14:10:21.02 spid9s FCB::Open failed: Could not open file E:\MSSQL\MSSQL.4\MSSQL\Data for file number 1. OS error: 5(Access is denied.).
2009-11-24 14:10:21.02 spid9s Error: 5120, Severity: 16, State: 101.
2009-11-24 14:10:21.02 spid9s Unable to open the physical file "E:\MSSQL\MSSQL.4\MSSQL\Data". Operating system error 5: "5(Access is denied.)".
2009-11-24 14:10:21.02 spid9s Error: 17207, Severity: 16, State: 1.
2009-11-24 14:10:21.02 spid9s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'E:\MSSQL\MSSQL.4\MSSQL\Data'. Diagnose and correct the operating system error, and retry the operation.
2009-11-24 14:10:21.02 spid9s Error: 17204, Severity: 16, State: 1.
2009-11-24 14:10:21.02 spid9s FCB::Open failed: Could not open file E:\MSSQL\MSSQL.4\MSSQL\Data for file number 2. OS error: 5(Access is denied.).
2009-11-24 14:10:21.02 spid9s Error: 5120, Severity: 16, State: 101.
2009-11-24 14:10:21.02 spid9s Unable to open the physical file "E:\MSSQL\MSSQL.4\MSSQL\Data". Operating system error 5: "5(Access is denied.)".
2009-11-24 14:10:21.02 spid9s File activation failure. The physical file name "E:\MSSQL\MSSQL.4\MSSQL\Data" may be incorrect.
2009-11-24 14:10:21.02 spid9s Error: 945, Severity: 14, State: 2.
2009-11-24 14:10:21.02 spid9s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2009-11-24 14:10:21.02 spid9s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2009-11-24 14:10:21.02 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
November 24, 2009 at 1:01 pm
Try the below url:
http://support.microsoft.com/kb/224071
in the above article he mentioned about a trace flag like –c –m T3608.
Here we need to just enable the –T3608 only, not whole –c –m T3608
Thank You.
Regards,
Raghavender Chavva
November 24, 2009 at 1:09 pm
Where did you move the Model Database to?
What is the previous and current location of Model DB. It seems SQL Server is trying to find it at the location "E:\MSSQL\MSSQL.4\MSSQL\Data"
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 24, 2009 at 1:12 pm
I moved it to that location e drive
November 24, 2009 at 1:20 pm
The service under which SQL Server is starting has permissions to that location right??
Just to confirm, what about MssqlsSytemresource DB it's in the same directory as Master DB?
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 24, 2009 at 1:31 pm
I need my sql server to run asap. Now I just want to be the way it was before for now. I removed everything from e drive and want to stay the way it was on c drive, error log is showing the following:
Starting up database 'model'.
2009-11-24 15:15:05.00 Server Server is listening on [ 127.0.0.1 <ipv4> 1554].
2009-11-24 15:15:05.00 Server Dedicated admin connection support was established for listening locally on port 1554.
2009-11-24 15:15:05.00 spid9s Error: 17207, Severity: 16, State: 1.
2009-11-24 15:15:05.00 spid9s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'E:\MSSQL\MSSQL.4\MSSQL\Data'. Diagnose and correct the operating system error, and retry the operation.
2009-11-24 15:15:05.00 spid9s Error: 17204, Severity: 16, State: 1.
2009-11-24 15:15:05.00 spid9s FCB::Open failed: Could not open file E:\MSSQL\MSSQL.4\MSSQL\Data for file number 1. OS error: 5(Access is denied.).
2009-11-24 15:15:05.00 spid9s Error: 5120, Severity: 16, State: 101.
2009-11-24 15:15:05.00 spid9s Unable to open the physical file "E:\MSSQL\MSSQL.4\MSSQL\Data". Operating system error 5: "5(Access is denied.)".
2009-11-24 15:15:05.00 spid9s Error: 17207, Severity: 16, State: 1.
2009-11-24 15:15:05.00 spid9s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'E:\MSSQL\MSSQL.4\MSSQL\Data'. Diagnose and correct the operating system error, and retry the operation.
2009-11-24 15:15:05.00 spid9s Error: 17204, Severity: 16, State: 1.
2009-11-24 15:15:05.00 spid9s FCB::Open failed: Could not open file E:\MSSQL\MSSQL.4\MSSQL\Data for file number 2. OS error: 5(Access is denied.).
2009-11-24 15:15:05.00 spid9s Error: 5120, Severity: 16, State: 101.
2009-11-24 15:15:05.00 spid9s Unable to open the physical file "E:\MSSQL\MSSQL.4\MSSQL\Data". Operating system error 5: "5(Access is denied.)".
2009-11-24 15:15:05.00 spid9s File activation failure. The physical file name "E:\MSSQL\MSSQL.4\MSSQL\Data" may be incorrect.
2009-11-24 15:15:05.00 spid9s Error: 945, Severity: 14, State: 2.
2009-11-24 15:15:05.00 spid9s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2009-11-24 15:15:05.00 spid9s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2009-11-24 15:15:05.00 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Viewing 15 posts - 1 through 15 (of 25 total)
You must be logged in to reply to this topic. Login to reply