0

After creating a nonclustered index on a SQL Server table, it leads to disk space used increase. Even after we dropped the index, the difference of disk space in use used didn't change.

Before creating the nonclustered index, total size on disk was 8.5GB:

enter image description here

After creating the nonclustered index, the total size on disk increased to 8.99GB:

enter image description here

Any idea how to free disk space used by dropped index?

Igor
  • 60,821
  • 10
  • 100
  • 175
Abba
  • 519
  • 6
  • 17
  • 1
    Unless you've run out, SQL Server is going to keep the memory forever (or until a reboot or you clear *all* memory). This is why there is a min/max memory setting. See here: https://stackoverflow.com/questions/14646195/sql-server-clear-memory – Jacob H Mar 14 '19 at 16:46
  • Server has already been rebooted but no change. Memory is still being used by SQL Server – Abba Mar 14 '19 at 16:47
  • Please update the post with your minimum and maximum memory settings. – Jacob H Mar 14 '19 at 16:48
  • I m not having issues with RAM Memory , but sizes of Data files on disk – Abba Mar 14 '19 at 16:58
  • 1
    Ok... so the physical files are not the same thing as memory. And shrinking the database files is generally considered not a good idea. Check here: https://dba.stackexchange.com/questions/17277/when-is-it-ok-to-shrink-a-database – Jacob H Mar 14 '19 at 17:03
  • I updated your question and replaced the word Memory with Disk Space as that is what you are ask about. Disk space and Memory are *not* interchangeable terms. – Igor Mar 14 '19 at 17:21
  • Clearly a database management/administration question. VTC as off-topic; belongs on DBA SE site. – UnhandledExcepSean Mar 14 '19 at 17:34

0 Answers0