shrink down database during copy
-
Hi, I want to copy production database to a testing server. The production database is too big. Is there a way that we can shrink down the db size (taking a year data for example) when we copy it to the testing server?
-
Suggest copy the ddl or just doing a copy objects with the Import/Export wizard to establish the database on the other server then using the Import/Export wizard you can move data but usign queries to limit the amount.
Otherwise, there is no such thing as a partial restore of the data in the tables.
-
Hi, I want to copy production database to a testing server. The production database is too big.... As usual, testing for performance takes it in the pants...
You'll find out what I mean when your developers write code that works really fast on the "Gold Set" you're trying to create only to see it crash and burn when you promote it to production because the code isn't scalable. 
No... not trying to be sarcastic, synical, or snotty 
I've seen this 'bout a million times just at my current job... I laugh at the people who thought doing this same thing was a good idea --Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply