I have a small doubt on how this works. We came to know last night one of our sql databases had bulk load operation done with vendor giving that data of approx 300 GB would be bulk loaded.

Before and after when i checked the space used within database using gui as well as sp spaceused i can hardly see any decrease in unused space as free space has merely went down below 10 Gb.

Also I thought may be ldf, if not mdf and ndf growths but did not find anything there. Please help me understand how this works

database is in full recovery model

  • Sounds like not that much data was loaded, or it was loaded and then deleted, or perhaps you're looking at the wrong database.... – Tony Hinkle Nov 19 '18 at 21:21
  • @TonyHinkle: looking at the correct database. just wandering if it was loaded and then deleted or updated should not that be bumping up the ldf's? – BeginnerDBA Nov 19 '18 at 21:43
  • The simple way to verify/check is to restore a database using the backup file before the restore, and then compare the table sizes (like row #) btw the current db and the restored db. If you believe there is no much change, then either the vendor's bulk load is not loaded correctly or the load volume is not 300GB (well, of course, you need to consider table level compression as well in your judgement logic) – jyao Nov 19 '18 at 22:23
  • A bulk load would not make the log (.ldf) files grow very much. – Tony Hinkle Nov 19 '18 at 22:30
  • 1
    Bulk load is fully logged in full recovery model, so it should log significantly to the log. Unless the database is "effectively" in simple mode (for instance switching to simple and back to full or the first full backup never produced). – Tibor Karaszi Nov 20 '18 at 7:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.