Let’s look at how you would shrink a Windows Azure SQL Database (WASD). Most data professionals reach for the second option. Create a new database, of a smaller defined size, and migrate your data (in the old days we called this a logical dump, more on that later).Once SQL Server allocates space on disk there are only two ways to reclaim that space for the O/S. What is interesting to note here is that even if we drop a table to free up space the data file on disk does not decrease in size. This leads to internal fragmentation, which happens to be the main ingredient of the dish we like to call “poor performance.” In order to shrink the file down, SQL Server will move the data pages around on disk. This command allows for SQL Server to release unused space and shrink the size of the file allocated on disk. When the files in question are SQL Server database files (data or log) then administrators reach for a familiar tool: DBCC SHRINKDATAFILE() It is not a question of “if,” but a matter of “when” this will happen. At some point in your career as a data professional you are going to fill up an entire drive with data.

Windows 10 reclaim disk space 449