September 10, 2018 at 12:47 pm
Hi,
Database size is increased after applying dacpac
database size - 285 GB (before dacpac applied)
database size - 532 GB (after dacpac applied)
Scan documents are stored in one table with file stream.
scan document size is approx 250 GB.
Seems that new folder with files in file stream folder.
how can reduce the size of database to original size (285 GB)
SQL Server ver is 2016
Regarsd
Binu
September 10, 2018 at 1:42 pm
How much free space in the database now versus prior to the DACPAC being applied?
September 10, 2018 at 2:40 pm
A DACPAC should only have schema changes, so I wouldn't expect that much space. Did you check what the changes were that could have been applied? That might help you. Also, if this was a BACPAC, which is a DACPACP + data, that would make sense.
To reduce the size, typically you are removing data from the database. A database, however, allocates more space than it needs, unlike a text file. You do need to check the free space in your file, regardless of size. That might help determine the next action.
It is possible that your DACPAC included resizing of files, but I didn't think that was included in a DACPAC. I could be incorrect here.
September 12, 2018 at 4:55 am
What were the schema changes? Did it add new indexes on top of the ones already there? That would explain the size increase. Or is it just the log that increased in size due to the transactions within the dacpac?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply