• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 201
  • Last Modified:

restored database & bigger drive

Yesterday afternoon, after an automated restore of a DB, the drive became bigger(The alerts show me that, the size of the space used crossed a particular limit on the drive). But after 5 hours, the drive became within the accepted range.

The log is in a separate LUN drive.

There were very minimal users yesterday in the system, and TempDB was well controlled too, in usage.

Is there anything that can trigger an expansion of drive space used after a restore process of a database?

thanks
0
anushahanna
Asked:
anushahanna
  • 4
  • 4
2 Solutions
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
>> the drive became bigger

Do you mean the Physical Drive became bigger compared to its defined size..
Kindly clarify what you meant by expansion of drive space..
0
 
anushahannaAuthor Commented:
The physical drive where the data sits and where this restore happened.

The restore overwrites the existing database, and is of the same size.

For example, the drive was 100GB used generally, and for some reason the drive had swelled to 200GB for 5 hours, and then come back to the 100GB range. The spike happened right after the restore which I can see from the logs & alerts.

Thanks
0
 
JluchtCommented:
Is it possible that it wrote a bunch of stuff to the transaction logs during the restore?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
anushahannaAuthor Commented:
The TLog are in separate drive (not part of the 100GB that we are talking about). This drive only contains the data file.
0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
>> the drive was 100GB used generally, and for some reason the drive had swelled to 200GB for 5 hours, and then come back to the 100GB range.

Kindly confirm the following..

* Do you have any DB Reindex task ran during this period
* Do you have Auto Shrink database enabled..

If your answer is yes for both of the above, then it might happen..
0
 
anushahannaAuthor Commented:
rebuild happened 7 hours before this event. Do you think this could have any indirect effect?

Auto Shrink is False.
0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
>> rebuild happened 7 hours before this event. Do you think this could have any indirect effect?

Yes.. It should..
When did it completed..
Rebuilding indexes requires huge amount of space in both Data and Transactional Logs..

>> Auto Shrink is False.

If this is set to False, do you have any Periodical jobs to do SHRINKFILE or SHRINKDATABASE operations without which your Data files grown to 200 GB would not shrink back to 100 GB..

Kindly check it out once..
0
 
anushahannaAuthor Commented:
When the rebuilding happened, the drive was still at 100GB. It was 7 hours later that it became around 200GB.

There was no manual intervention or scheduled SHRINKFILE or SHRINKDATABASE to bring the size from 200GB to 100GB. These happened on a weekend when there was less activity and no one administering.

I tried seeing the error logs but could not get any clues from there.

If this happens again, I can run a profiler at that time to capture it..

If you have any other thoughts, kindly let me know..

thanks for your help.
0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
>> I tried seeing the error logs but could not get any clues from there.

Any Data Movement related operations might have occured like

* BULK Load of data into tables
* DB Reindex Task

without any one of the above operations its not possible to grow from 100 GB to 200 GB..

Kindly look at all your Maintenance activities once whether there are any operations related to the above so that we can find the exact reason for this.

>> If this happens again, I can run a profiler at that time to capture it..

Yes, you need to do it when it happens again..
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now