DB Deployment using SSMS

Discussion in 'Databases' started by PixelPlex, Jul 9, 2008.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. Say I've got my app working on my local SQL server instance. It contains a single database that has all of the aspnet tables, as well as some custom, app specific tables. It's also got various sprocs and functions. How would I deploy this database to my site's DASP DB using SSMS in the following ways:

    1. wipe preexisting database clean and replace with my local copy

    2. retain site data, add new objects and replace existing objects/schema only if they've been updated

    Thanks for the info.
     
  2. I always recommend keeping a blank DB backup for things like this.
    First thing you should do when you start a new DB is make a backup.
    Then you can fall back on it at anytime.
    Other than that you have a lot of manual work to do or ask the support team to drop your DB.

    As for moving records and objects, in SQL Server 2005 I've done that here successfully with the Import/Export wizard.
    Just make sure you check the options like Optimize for many rows, etc.
    More than once I migrated large forums, Snitz and UK, and never had any trouble.
    Your mileage may vary however as I've seen others complain about some things.
    I always found double-checking the options resolved that, for me anyway.

    You can of course createmultiple sets of scripts, but that is a bit more complicated.
    Salute,
    Mark
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page