April 6, 2010 at 9:34 am
On our sql servers, we frequently create new customer databases which are blank copies of our main database model (with dictionary tables pre-populated).
We're trying to make up our minds about whether or not to have a blank one on each sql server, and simply to a restore from its last backup to create new customers databases, or whether to run a complete database creation script to create new databases.
Our database model has 1500+ tables and 2500+ stored procedures.
Suggestions? Opinions? Pros and Cons?
April 6, 2010 at 9:39 am
I might just add to this that when upgrading sql databases, we would run the same upgrade script against all databases on a sql server, which would include the blank one, therefore the next database creates will come from the blank one.
And using the other method, a new database would be created with the last master script plus subsequent update scripts.
April 6, 2010 at 1:00 pm
Either of those options could work. You might also look at using the model database. Create all the structures and code there and then automatically get it deployed any time you create a database.
"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 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply