October 27, 2008 at 2:27 pm
Error log: 2008-10-27 15:02:33.80 server Copyright (C) 1988-2002 Microsoft Corporation.
2008-10-27 15:02:33.80 server All rights reserved.
2008-10-27 15:02:33.80 server Server Process ID is 3636.
2008-10-27 15:02:33.80 server Logging SQL Server messages in file 'E:\MSSQL\log\ERRORLOG'.
2008-10-27 15:02:33.85 server SQL Server is starting at priority class 'normal'(4 CPUs detected).
2008-10-27 15:02:33.92 server Working Set size set to 1050624 kilobytes.
2008-10-27 15:02:33.96 server SQL Server configured for thread mode processing.
2008-10-27 15:02:33.96 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2008-10-27 15:02:34.07 server Attempting to initialize Distributed Transaction Coordinator.
2008-10-27 15:02:36.46 spid3 Starting up database 'master'.
2008-10-27 15:02:36.66 server Using 'SSNETLIB.DLL' version '8.0.818'.
2008-10-27 15:02:36.66 spid5 Starting up database 'model'.
2008-10-27 15:02:36.66 spid3 Server name is 'SXATRNMAST'.
2008-10-27 15:02:36.69 spid5 Error: 602, Severity: 21, State: 50
2008-10-27 15:02:36.69 spid5 Could not find row in sysindexes for database ID 3, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes..
2008-10-27 15:02:36.69 spid5 Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
.
I have sql 2000 and sql 2005 in same server(win2003), but different instance. I run (sql 2000) sqlservr.exe -c -m to make single user mode for system databases, then I copied all system db files (mdf,ldf) to another location(for sql 2005). then I tried to restared sql 2000 server, it showed the error above. pls advise!
October 27, 2008 at 4:24 pm
You have a problem with your model database. Are the model.mdf and model.ldf there?
October 27, 2008 at 7:23 pm
thanks for asking, I am kind of new here. yes, model.mdf and model.ldf are still under data folder of sql 2000. One thing I don't understand is I did not change anything with system dbs at all, just make a copy and paste to another location. When i tried to restart it, the message is "service on Local computer started and then stopped. some services stop automatically if they have no work to do, ..."
thanks,
October 28, 2008 at 3:37 am
marg131 (10/27/2008)
thanks for asking, I am kind of new here. yes, model.mdf and model.ldf are still under data folder of sql 2000. One thing I don't understand is I did not change anything with system dbs at all, just make a copy and paste to another location.
Can you explain exactly what you did please?
What's the path for the 2000 system databases? What's the path for the 2005 system databases?
What does the following return (on SQL 2005)
select name, physical_name from sys.master_files where database_id = 3
If you can start the SQL service in restricted mode (-m -f) then please run this query.
select name, filename from sysaltfiles.
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
October 28, 2008 at 8:00 am
sql2000 path E:\MSSQL\Data
sql2005 path E:\MSSQL.1\Data
Against sql2005, I run
select name, physical_name from sys.master_files where database_id = 3
modeldevE:\MSSQL.1\MSSQL\DATA\model.mdf
modellogE:\MSSQL.1\MSSQL\DATA\modellog.ldf
I tried to start sql2000 service with -m -f, but still received same error log message above.
thanks,
October 29, 2008 at 6:50 am
Database compitability of SQL Server 2000 model database is 80. In SQL Server 2005 it is 90. Because the database structure is different. So you should not have copied the model database.
Just copy the model database of some other SQL Server 2000 server. It might work.
October 30, 2008 at 8:40 am
thanks. it worked for me. I just copied model from other db and reinstalled it. I'm facing side by side upgrade Sql 2000 to sql 2005, so what would be the best way to move system dbs? I have both instances installed on same win2003 server, different path for the data files.
October 30, 2008 at 9:46 am
Backup and restore's the safest. If you haven't made changes to model on SQL 2000, you can ignore that one. Unless you're moving all the jobs, etc, ignore msdb as well.
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 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply