SQL- Server – Free disk SPACE USING SHRINK

 Understanding shrinking the log

If you need to recover disk space from the transaction log file, consider shrinking the log file.

Shrinking logs helps after you perform an action that creates a large number of logs.

You can only shrink the log if there is free space on the log file.

Shrink the transaction log

Use the following steps to truncate the transaction log file:

  • 1. Right-click the database and select Tasks -> Shrink -> Files.


  • 2. Change the type to Log.
  • 3. Under Shrink action, select Release unused space and click OK.


What if the log size does not decrease?

If the size of the log does not change much after this, it means that your database has the recovery mode set to Full and there is not enough unused space to recover.


At this point you can consider the option to delete all logs by “temporary” set the database Recovery mode to Simple and try another shrink.


But Keep in mind that following these steps might result in data loss and you’ll not be able to recover data at a point in time 


  • 4. Right-click the database and select Properties -> Options.
  • 5. Set the recovery model  Simple and exit the menu.


  • 6. Right-click the database again and select Tasks -> Shrink -> Files.
  • 7. Change the type to Log.
  • 8. Under Shrink action, select Release unused space and click OK.


  • 9. When the process completes, switch the recovery model back to Full or Bulk-Logged and take a full database backup.








Location: Karachi, Karachi City, Sindh, Pakistan

Comments

Post a Comment

Popular posts from this blog

D365FO – AX – Update Data Entity Target Entity fields with X++

Image
  Imagine you want to set the value of a field of the Target Entity of a Data Entity with X ++ code You have to create an extension class that extends the data Entity, extends the “mapEntityToDataSource” method, and adds your code inside. [ExtensionOf(tableStr(PurchPurchaseOrderHeaderV2Entity))] //Extends Data Entity final class Al0PurchPurchaseOrderHeaderV2Entity_Extension {     public void mapEntityToDataSource(DataEntityRuntimeContext _entityCtx, DataEntityDataSourceRuntimeContext _dataSourceCtx) //Extends method     {         switch (_dataSourceCtx.name())         {             case dataEntityDataSourceStr(PurchPurchaseOrderHeaderV2Entity, PurchTable):             PurchPurchaseOrderHeaderV2Entity purchPurchaseOrderHeaderV2Entity = _entityCtx.getEntityRecord(); //Get Data Entity buffer (Source Entity)             PurchTable purchTa...
Read more

How to Create Auto Lookup Using EDT with Table Reference in D365 F&O

Image
  How to create a lookup in D365FO using X++? Lookups are the standard way to display a list of possible selection values to the user. For a user, while editing or creating database records, a lookup makes the data entry easy and errorless. In Microsoft dynamics 365 finance and operations, there are many ways of creating lookups. EDT and Table Relation Type lookups are the simplest forms of lookups in Microsoft dynamics 365 finance and operations. In this article, I will describe the very simplest type of lookup, which is EDT lookup, for making an EDT type lookup, a developer does not need to worry more about writing x++ coding,   Normally, standard lookups are created automatically by the system in Dynamics 365 for Finance and Operations and are based on the extended data types and table setup.  They are based on table relations and appear automatically. No additional modifications are required. Setting Up an EDT Lookup If you are a beginner use  Microsoft's free ...
Read more