on 06-13-2023 4:06 PM
We recently took a client copy from our PRD ECC database of 222,040 MB and copied to a test system.
The resulting total size of that test database after the copy was 257,972 MB. We are on MSSQL, with the test database set to Simple Recovery Model. Has anyone experienced such a dramatic increase in size of the database in the target system. If so, does anyone know what the reason for this is?
Hi Dustin,
Have you checked the table VBTP size before doing the client copy? or on the target system are you having more than one client after performing the client copy?
Regards
SS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The PRD size you mentioned is from the running DB or is the backup size? Usually, the backup is always smaller than the size of the running DB because of the space that the engine needs to operate.
The recovery model doesn’t impact the DB data size.
You can take a report from the top 50 tables using Management Studio on both servers and compare.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've run several queries to analyze the largest tables in both the test database instance and the production instance. Many of the tables that were copied from PRD appear to be using more space in DEV.
One example, VBRP in PRD is 3,741 MB, but in the test system it's 4,080 MB. There has been no user activity since the client copy. I'm not sure how, but the row counts in those tables are different as well. We only have one client on the test machine, so the rows aren't from a different client. I'll continue to do some research here.
User | Count |
---|---|
91 | |
9 | |
8 | |
7 | |
7 | |
3 | |
3 | |
3 | |
2 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.