Restored database taking massive amount of space
I restored a database with a 1.5gb .bak file. Everything works fine except the restored database now takes 64gb of space.
I've heard about shrinking databases and log files but how should I find out what is it that takes so much space and what I can "shrink" so that the data itself won't change. I need this production backup data in my development environment as it is.
I don't need full logs in the development environment where I'm doing the restoring. How to find out is it the data or the logs that take more space?
I'm using SQL Server Management Studio 2017
Maybe logs?
I suggest you to analyze if that fits you. Make the backups much shorter: See More
BACKUP DATABASE XXXXX TO DISK 'C:\XXX.bak' WITH COPY_ONLY
You can also change the Recovery Model from Full (Default) to Simple, after the restore.
Then SHRINK it
I'm honestly not sure if all of those are necessary, but that works for me to reduce space. Maybe shrinking before changing recovery model is better, or maybe one of those are not the best pratices.
- Math.Sin() gives incorrect value
- How to run my python script when the sunOS is start booting
- Express-session: not resetting cookie expiration on each request
- Getting a stack overflow exception when normalizing a vector
- Edit default summary function in R gives error for multiple variables
- What was a For loop? Why isn't it needed in R?
- How to use download button in shiny and save results in various formats (csv, texte, pdf, spss...)?
- Why are there two assignment operators, `<-` and `->` in R?
- lm()$assign: what is it?
- How to get the value of list(...) in R and S functions
- Design matrix for MLM from library(lme4) with fixed and random effects
- how to generate elements not included in my sample
- Create a matrix with gradually changing values without a for loop
- Emacs ESS and S-plus ( S+ ) 8.1 compatability
- How to lag date-index in a time-series in R?
- Nonlinear regression in R / S
- Calling R from S-Plus?