About Me

My photo
Kottarakara, Kollam, Kerala, India
Though currently in Thiruvananthapuram, my residence is at Kollam district in Kerala which is almost 75 kms away from the office

I Me Myself !

Hi all, as a ASP.NET professional i would like to use this as a technological and informative site. Maybe, this contains my personal portfolio, funny matters, videos, photos too. Still i mainly intend to use this for official purpose.

Currently specialising in Microsoft's Dynamic CRM 4.0, am engaged in an assignment to successfully develop and deploy a CRM product as per the custom business logic. I am employed in a microsoft partnered switzerland based firm, know more...

The technologies/languages/packages i am confident in are:


  1. ASP.NET (vb/C#)

  2. C#.net

  3. vb.net

  4. sql server

  5. Adobe photoshop

  6. Macromedia Flash

  7. MS Dynamics CRM 4.0

My achievements includes:
1) Cisco Certified Network Associate (CCNA).
2) Active member of ASP.NET forum.
3) Active member of CRM Dynamics Community.

My professional career:


  • Web Designer at AUFIDUS INDESIGNS, Ernakulam, Kerala

  • Computer Lecturer at SRV Govt Higher Secondary School, Ernakulam, Kerala

  • Software Instructor at IGNOU, Ernakulam, Kerala

  • Lower Divison Clerk (LDC) at Melattur Grama Panchayat, Malappuram, Kerala

  • Software Trainer in .NET at Sun Infosys, Kottayam, Kerala

  • Software Trainer in .NET at NIIT, Adoor, Kerala

  • Computer Lecturer at UIT, Adoor, Kerala

  • Senior Systems Executive at PIT Solutions, Technopark, Thiruvananthapuram, Kerala

SQL Transaction Log file : Reducing size of LDF file

For any High volume db operated websites that contains millions of data, that also in binary formats too, it’s common that the transaction log files (.ldf files) will grow at an incredible rate without our notice and at some stage makes our hard disk fully occupied. So taking a backup of this database and restoring it somewhere else is not possible if the hard disk in target server has not enough space to accomplish the db. In one of our real-time scenarios we have got upto 50 GB of log file size in production server. We can’t ever guarantee the client that how much hard disk space he needs to keep in his server .
So the most feasible solution is always keep that high volume LDF files in your backup and assign a new LDF file to the db.
These steps can be used to remove the LDF and replace it so that it is smaller. These steps were done using SQL Server 2005 Management Studio.
• Right click the database
• Select Properties
• Go to the Options Page
• Note what the recovery model is set to. Mine was "Full"
• Click OK
• Right click the database
• Select Tasks
• Select Back up
• Change the Backup Type to "Transaction Log"
• Select current destination backup file listed.
• Click Remove. Note – depending on your nightly backup you may have to put this back. I did not since my backups do not depend on this.
• Click Add
• Enter in a UNC path to another server to store the backup. Example: //Server1/common/MyDataBase_Log.bak
• Click OK
• Click OK to start the backup
Once the backup completed.
• Right click the database
• Click Detach
• Check the Drop Connections check box
• Check the Update Statistics checkbox
• Click OK
• Moved the bloated LDF file off the server (or delete it)
• Right click the server in Management Studio
• Selected Attach
• Click Add
• Locate the MDF
• Click OK
• Select the LDF in the bottom pane
• Click remove (a new one will get built)
• Click OK
• The LDF is auto rebuild and is small.
• Right Click the database
• Select Properties
• Go to the Options page
• Set the Recovery back to the way it was originally. I changed mine from Simple to Full.
Labels: , ,
Subscribe to: Posts (Atom)