![]() Also, when I attempt to look at the properties of the database, I get denied because the database "is in transition". Is the rebuild actually taking place? If I have a db backup scheduled for later tonight, should I pause that so the log file can continue to get rebuilt or should that be completed by then? Remember, the original log was 147 GB.Īfter nearly 20 hours, it is still running. However, that was not being recognized, so I had to rebuild one. When I realized that was done, I had more space created and moved the file back onto this server. ![]() The original log file was moved to a different server (not copied). The database for the log file has recovery set to Bulk_Logged. The log file was causing disk space errors due to it continuously growing. The customer has very limited space available. Those messages continue to get produced, but is that normal when rebuilding a log? Is the rebuild expected to take a long time when the previous log file was 147 GB? Or is this in a continuous loop? Nonqualified transactions are being rolled back. It's been running for over 30 mins now and the messages that are provided are a whole bunch of these: This is what I'm doing: use masterĪLTER DATABASE my_db SET SINGLE_USER WITH ROLLBACK IMMEDIATE ĪLTER DATABASE my_db REBUILD LOG ON (NAME=my_db,FILENAME='C:\MSSQL\Data\my_db_log.ldf')ĪLTER DATABASE my_db SET MULTI_USER WITH ROLLBACK IMMEDIATE I want to know if what is happening is normal. I'm trying to rebuild a log file for my database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |