SQL Server Developer edition on Windows 7 ENT.
I can’t able to start SQL server anymore. If I start the service manually, it starts then shuts down. The error log says:
The transaction log for database ‘model’ is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in
2010-09-25 09:38:14.84 spid8s Could not write a checkpoint record in database ID 3 because the log is out of space. As database
administrator to truncate the log or allocate more space to the database log files.
2010-09-25 09:38:14.84 spid8s Could not create tempdb. may not have enough disk space available. Service should be on, as soon as possible becouse it’s bread and butter are no-more for me today. Only way to start cmd, so let start this …
I start resolve this by starting SQL Server in single-user mode. In this mode CHECKPOINT is not run. You should be able to review the settings for the model database, and user ALTER DATABASE to change those settings.
Be sure that you don’t have SQL Server Agent running, or something else that connects automatically.
To enable single-user mode, open SQL Server Configuration Manager, select the service, open it, and go the Advanced tab. Add ;-m to the startup
options and restart SQL Server.
You can start, stop, and pause SQL Server as you would any other service. On a local system, you can type the necessary command at a standard command prompt. On a remote system, you can connect to the system remotely and then issue the necessary command. To manage the default database server instance, use these commands:
NET START MSSQLSERVER Starts SQL Server as a service.
NET STOP MSSQLSERVER Stops SQL Server when running as a service.
NET PAUSE MSSQLSERVER Pauses SQL Server when running as a service.
NET CONTINUE MSSQLSERVER Resumes SQL Server when running as a service.
To manage named instances of SQL Server, use the following commands:
NET START MSSQL$instancename Starts SQL Server as a service, where instancename is the actual name of the database server instance.
NET STOP MSSQL$instancename Stops SQL Server when running as a service, where instancename is the actual name of the database server instance.
NET PAUSE MSSQL$instancename Pauses SQL Server when running as a service, where instancename is the actual name of the database server instance.
NET CONTINUE MSSQL$instancename Resumes SQL Server when running as a service, where instancename is the actual name of the database server instance.
You can add startup options to the end of net start MSSQLSERVER or net start MSSQL$instancename commands. Use a slash (/) instead of a hyphen (–) as shown in these examples:
net start MSSQLSERVER /f /m
net start MSSQL$CUSTDATAWAREHOUS /f /m
Instead of referencing MSSQLSERVER or MSSQL$instancename, you also can reference the service by its display name. For the default instance, you use “SQL Server (MSSQLSERVER)” with net start, net stop, net pause, and net continue. Named instance, you use net start “SQL Server (InstanceName)”, where InstanceName is the name of the instance, such as net start “SQL Server (CUSTDATAWAREHOUS)”. In both usages, the quotation marks are required as part of the command text.
I save my Bread & Butter, cmd save me, u know what i mean.