1

On MSSQL (our DB size is 520g), there is one filestore table that holds tons of files. 65-70% of this 520g is sitting in there. So essentially, it's a 200g database with 320g worth of files in this one table.

I have ran a script that removed around 120g worth of old records from this table. The DB is still sitting at 520g, but there's this 120g hole inside that is available for writes.

  1. Should there be a significant improvement in overall DB performance after clearing up this much space in the DB?

  2. How does having a huge amount of data in one table effect the performance of queries that have nothing to do with that table?

2
  • 2
    Can you be elaborate on what you mean by "filestore table"? Commented Nov 22 at 0:27
  • 1
    You write you already removed a bunch of data. Did it improve performance for you? Commented 2 days ago

2 Answers 2

0

Queries to the table this table will probably be faster. But nothing else should change. You may see better improvement if you shrank that file as well.

1
  • I believe shrinking the file will not help. Commented yesterday
0

(1) Should there be a significant improvement in overall DB performance after clearing up this much space in the DB?

Not really.

If you have suitable indexing in place, potential performance gains are negligible.

If you don't have suitable indexes, potential performance gains are larger, but you should add/tune your indexes for even greater performance improvements anyway.

(This is assuming you work with small amount of records at the time. Which I imagine is intended usage pattern for such table.)

How does having a huge amount of data in one table effect the performance of queries that have nothing to do with that table?

Not at all.

If you won't touch the data, it will quietly sit on disk and have basically no overhead.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.