anxious! !! Boss help out!

githzerai

LogWriter: An operating system error 33 was encountered (part of the file has been locked by another program and the process cannot access it.).
Write error during log flush. Shutting down server
Logs for database 'XXXX' are not available. .
Error: 9001, severity: 21, status: 4
The log for database 'XXXX' is not available ..

Why is it happening like that? ? ? ? ?

nankeny

Restart

Check for viruses

ykll0051

Has it always been?
It is estimated that the database file is broken.

我是杀人狂

SQL Server rebuilds the tempdb database every time the service is restarted
    
  If the tempdb grows automatically due to the need during the system operation, SQL Serve will not remember the size after growth, and it will return to the original size after restarting the service.
  But if the user used to manually adjust the size of tempdb, restarting the service SQL Server will rebuild tempdb to the user specified size
    
  Test example
    
  tempdb initialized to 8MB
    
  1) Make tempdb grow automatically
    
  select b. * into #t from sysprocesses a, sysobjects b
    
  Use sp_helpdb 'tempdb' after restart
  You can see that tempdb is restored to 8MB
    
  2) Users use Alter Database to adjust to 100MB,
    
  USE master
  GO
  ALTER DATABASE tempdb
  MODIFY FILE
        (NAME = tempdev, SIZE = 100MB)
    
  After restarting the service, the size of tempdb is 100MB.
    
  The following query can see the changes in tempdb
  select a.filename, a.name, a.size * 8.0 / 1024.0 as originalsize_MB,
  f.size * 8.0 / 1024.0 as currentsize_MB
  from master..sysaltfiles a join tempdb..sysfiles f on a.fileid = f.fileid
  where dbid = db_id ('tempdb')
  and a.size <> f.size

ykll0051

Every time I start it?

hhuaixiaozi

Restart the operating system

kxiaper

try:
Change the location of Tempdb:
  1. Use Enterprise Manager or sp_helpdb to see where tempdb is now stored
  2. Execute the following statement in the query analyzer
  alter database tempdb modify filename = 'tempdev', filename = 'newpath\newfilename')
  alter database tempdb modify filename = 'templog', filename = 'newpath\newfilename')
  3. Shut down sqlserver and restart
  4. Delete the old tempdb file

githzerai

I am the landlord
Shut down the database server, restart the operating system, and open the database server. At this time, the rollback is started. At this time, the Enterprise Manager and the Query Analyzer cannot be opened. After the rollback is completed, open the Enterprise Manager and see the database in doubt. Once encountered this problem. I have a large amount of data, and there is a table with more than 90 million rows.

githzerai

I am the landlord
In addition, it is not a problem of TEMPDB. I have moved to another disk very early.