Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 101
  • Last Modified:

Shrink A database in SQL

I have an SQL server  2008 r2 with 300 gigs of space however, I'm down to 77 gigs (yikes).  The particular database currently is 150875.06 MB I went to the properties and shrink database and I'm running this but it's been running for over an hour.  I'm not sure if this is correct.  Is there another way for me to get some room.  I already have the options set for recovery model simple on all the 10 database partitions.  I'm not a DBA by any means and there are 10 partitions already. the main database is the largest and the one I'm trying to shrink. I'm using SQL Management Studio for this task.  Is there a better, faster way?
0
WellingtonIS
Asked:
WellingtonIS
2 Solutions
 
DamjanCommented:
Don't shrink your databases to free up disk pace.  It's a bad idea. It is generally known as a worst practice to ever shrink a production database or data file...

Follow these tips to reclaim disk space
https://www.mssqltips.com/sqlservertip/1810/out-of-space-on-the-c-drive-of-your-sql-server-and-ways-to-reclaim-disk-space/

Maybe you could just create a new database and migrate data to it.
0
 
WellingtonISAuthor Commented:
Can I stop it in the middle?
0
 
Scott PletcherSenior DBACommented:
Shrinking can only help if you have significant amounts of unused space.

You also need to distinguish between data space and log space.  Shrinking a vastly over-sized log can make sense any time.  Shrinking data is very rarely done.

To check for unused data space, run this command:

USE <your_db_name>
DBCC SHOWFILESTATS /*this command does NOT list log space*/
If the "UsedExtents" are significantly lower than the "TotalExtents", it might make sense to shrink the file.

YOU SHOULD ALWAYS SHRINK FILE BY FILE, NEVER THE ENTIRE DATABASE.

You can check all file sizes, including the log file, like so:
EXEC sp_helpfile
If the log file is extremely large/oversized, you can shrink the log file directly.
DBCC SHRINKFILE(2, <total_mb_to_remain_in_log_file>)
0
Veeam Task Manager for Hyper-V

Task Manager for Hyper-V provides critical information that allows you to monitor Hyper-V performance by displaying real-time views of CPU and memory at the individual VM-level, so you can quickly identify which VMs are using host resources.

 
Scott PletcherSenior DBACommented:
Yes, you can safely cancel a shrink.
0
 
WellingtonISAuthor Commented:
I ran EXEC sp_helpfile but I do not see any sizes for logs?  As for deleting the logs manually I have no idea where they are
sql.png
0
 
WellingtonISAuthor Commented:
I ran this and it didn't do anything EXEC sp_cycle_errorlog
0
 
Scott PletcherSenior DBACommented:
EXEC sp_helpfile /*not sp_help*/
0
 
WellingtonISAuthor Commented:
Now how do I shrink the logs? Is there a command?  The logs are about 102400 KB for all 10 but on my master database I have 37712192 KB
0
 
Scott PletcherSenior DBACommented:
ALTER DATABASE master SET RECOVERY SIMPLE;
USE master;
DBCC SHRINKFILE(2, 2048);

Check msdb and tempdb log sizes as well.
0
 
WellingtonISAuthor Commented:
it's executing.  I hope this works.  I replaced master with the name of the database - great I reclaimed 133 gigs of space.  thanks you rock! :)  I'll need to save this so I can use it again.
0
 
WellingtonISAuthor Commented:
Thanks.  This really helped.
0
 
Scott PletcherSenior DBACommented:
Really glad it helped! ...

... But, for a user db, you want to go back and allocate additional space, since 2GB is probably not enough, especially if the allocation was over 100GB before.

First run these commands:

USE [db_name]
EXEC sp_helpfile
--Copy/save the name in the first column for file#2, the log file.

Then run these commands to gradually increase the log size (yes, there are technical reasons for not going to the total size in one command):
ALTER DATABASE [db_name] MODIFY FILE ( NAME = <copied/saved name from above>, SIZE = 6GB )
ALTER DATABASE [db_name] MODIFY FILE ( NAME = <copied/saved name from above>, SIZE = 10GB )
ALTER DATABASE [db_name] MODIFY FILE ( NAME = <copied/saved name from above>, SIZE = 14GB )
ALTER DATABASE [db_name] MODIFY FILE ( NAME = <copied/saved name from above>, SIZE = 18GB )
0
 
Steve WalesSenior Database AdministratorCommented:
Since it doesn't seem to have been mentioned yet ...

Make sure you're backing up your transaction log frequently so that it doesn't need to grow and grow.

A transaction log file will grow forever when your database is in full recovery mode if you're not making transaction log backups.
0
 
WellingtonISAuthor Commented:
Actually this database is for Websense and I can detach the older DB's from 2015 so that's going to be my next step.  I don't need to hold information on web activity for years. 6 months is more than enough

USE [db_name]
 EXEC sp_helpfile
 --Copy/save the name in the first column for file#2, the log file.

 Then run these commands to gradually increase the log size (yes, there are technical reasons for not going to the total size in one command):
 ALTER DATABASE [db_name] MODIFY FILE ( NAME = <copied/saved name from above>, SIZE = 6GB )
 ALTER DATABASE [db_name] MODIFY FILE ( NAME = <copied/saved name from above>, SIZE = 10GB )
 ALTER DATABASE [db_name] MODIFY FILE ( NAME = <copied/saved name from above>, SIZE = 14GB )
 ALTER DATABASE [db_name] MODIFY FILE ( NAME = <copied/saved name from above>, SIZE = 18GB )

Does this equal the logfile name?
0
 
Scott PletcherSenior DBACommented:
Yes, the logical log file name, not the physical file name.  You'll see the logical name in the first column in the output from "exec sp_helpfile".  The log file will be file#2.
0
 
WellingtonISAuthor Commented:
OK thanks.  I got some serious room back.
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now