We are currently in the process of testing a new version of the accounting product we use and this new version requires that we take a copy of our live DB and run it thru the client Schema Update process. For reasons of limited resoucres we are doing this on a develpment server which is slower and has less space then the live server does.
I have no contol over the schema update and so what I'm looking for is suggestions on how best to minimize the amount of space this update will consume via the growth of the log file and the temdb. I can tell you that the schema update is many, and I mean many T-SQL DDL/DML calls.
This is a test DB so its OK if something happens, when can we referesh it and so I'm not concerned with recovery real time or otherwise with this one. What I'm looking for is how best to set this so that a large number of TSQL commands (that I have no control over aside from starting) can run and cause the minimal amount of growth across the DB & the server due to limited space on the server.
Suggestions?
Thanks
Kindest Regards,
Just say No to Facebook!