SQL in dev and live environment

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • vertigo262
    New Member
    • Jul 2007
    • 62

    SQL in dev and live environment

    Ok,

    this is going to sound like a stupid question to some, so apologies to those.

    Ok, I am building a website in .net and Microsoft SQL. the site is almost ready to go live.
    But like all websites, there is continually development and updates.

    so, my question is as far a development

    what's the best way to update the dev database, and then the live.

    for example, I use management studio to update the database. do I need to update the dev, then the live one manually.

    Or is it normal practice to script the table updates on the dev, and then use the script on the live database. Or

    is there a way to update the dev, and generate a script of changes for the live database.

    any input on this would be greatly appreciated
  • ck9663
    Recognized Expert Specialist
    • Jun 2007
    • 2878

    #2
    Once your application goes live, it is always advisable to have a development environment and a testing environment. Your testing should mimic your live environment while your dev can be anything. Try to do a replication if possible. That way, you can be sure it's always sync.

    Good Luck!!!

    ~~ CK

    Comment

    • vertigo262
      New Member
      • Jul 2007
      • 62

      #3
      wait,

      replication of the data? or replication of the database structure? if that can be done.

      my problem is, let's say I add some fields in the dev box. how do the changes get migrated over to the live box?

      Comment

      • ck9663
        Recognized Expert Specialist
        • Jun 2007
        • 2878

        #4
        It actually depends on what you need to sync. If it's dev, sometimes the sync you need to do are just codes. If there's a big patch, the sync you need to do is data. If you can give more details, we'll be able to help more...


        Happy Coding!!!

        ~~ CK

        Comment

        • vertigo262
          New Member
          • Jul 2007
          • 62

          #5
          OK, What I have is a .net website with a SQL database.

          Two versions of the website and database are set up.

          Obviously, I want the live site to be up as much as possible.

          So what I was thinking I would do is my mods on the sql dev and see if they work, then manually update it using management studio as I don't really know much about sql scripts. the web code is simple enough. just do it in dev and copy it over.

          So I was wondering, is it better to write a sql script for the dev, and if it works, apply it to the live box.

          Now. this is where I get confused. I was told, and he was tpretty adamint, that it is unwise to mod the live box.

          Instead, mod the dev, and copy it over.
          Not only did that sound like a pain in the ass, but what happens when you work on the dev, and there is new data getting put in the live. then when you transfer over the dev to live. you are missing the new data.

          LOL. so now I am completly confused

          let me know if you need more info.

          Comment

          • meabi
            New Member
            • Dec 2010
            • 4

            #6
            Brief Description
            The Web Data Administrator is a utility program implemented in ASP.NET that enables you to easily manage your SQL Server data wherever you are.

            Comment

            • vertigo262
              New Member
              • Jul 2007
              • 62

              #7
              Hi meabi

              this seems off topic

              Comment

              Working...