Recently I developed a script to move user objects to newly created data file, then shrink the original file (command: DBCC SHRINKFILE (N'DataFile' , 100)) to reduce the disk space usage. however I found:
1. on the logshipping server, the second data file is created.
2. the original data file is not changed. though the data file on the primary server has shrunk to 100MB
We developed a tool ourself to do the logshipping, e.g. sending all trn files to another data center and restore the trn file, the databases in DR site remains in restoring status.
Does anyone knows what prevent the data file to be shrunk at DR site?