Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. database deployment

database deployment

Scheduled Pinned Locked Moved Database
databasesysadminsql-servercomtutorial
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    murali_utr
    wrote on last edited by
    #1

    hi, how to publish sql server database in server. thanks in advance!

    Have A Nice Day! Murali.M Blog

    C J 2 Replies Last reply
    0
    • M murali_utr

      hi, how to publish sql server database in server. thanks in advance!

      Have A Nice Day! Murali.M Blog

      C Offline
      C Offline
      Corporal Agarn
      wrote on last edited by
      #2

      What do you mean by "publish"? The data from a SQL Server database can be replicated many ways (backup/restore, detach/attach, ...). You need to have a SQL Server accessible by the client. If you mean publish as with a .NET program that is a different problem.

      1 Reply Last reply
      0
      • M murali_utr

        hi, how to publish sql server database in server. thanks in advance!

        Have A Nice Day! Murali.M Blog

        J Offline
        J Offline
        jschell
        wrote on last edited by
        #3

        Development phase. 1. Create one or more scripts that create the database 2. Create one or more scripts that populate the database. 3. CHECK them into source control. 4. Label them 5. Extract USING the label and store as a 'delivery' in the file system some where. Call this location X (it will be related to a delivery version number.) Install phase 1. Notify the production personal what X is (related to the verifie version.) 2. Production personal use a dabase id SPECIFICALLY for installs, and nothing else, to run the scripts appropriately. 3. Verify that the database is 'working' using something methodology probably involving other applications. There are all sorts of variations on the above.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups