Since I use jsp almost 100% of the time, i just write the changes in a jsp page, which i can then run on whatever needs it.
It's just a list of changes like: ALTER TABLE X ..... execute ALTER TABLE Y..... execute etc... Then just run it. Could use whatever language/app server you are using to do the same thing like Cold fusion or asp or perl or whatever. I rarely use the actual db tools because a script on one may not work on another, but in general, writing it using your app server and running it through that, you won't have to change your script. Travis ---- Original Message ---- From: "Cottell, Matthew" <[EMAIL PROTECTED]> Sent: 2001-11-20 10:10:29.0 To: SQL <[EMAIL PROTECTED]> Subject: RE: RE: Database Structure Replication Is the only way to run a script through Query Analyzer? > -----Original Message----- > From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]] > Sent: Tuesday, November 20, 2001 12:03 PM > To: SQL > Subject: RE: RE: Database Structure Replication > > I'm thinking that as convenient as that may be, it's probably not a very > good idea anyways. A test database is for exactly that, testing, so you > can make changes to the db and not have to worry about anything, but if > you had a self replicating db (even if only to change the structure), you > might run into some problems down the road. > > Maybe a dropped column here or there, or maybe you just mess up the whole > db and need to recreate it, then you have to do the same to the > production. Best thing to do here is just to write the changes into a > script (a jsp or cf file is fine too, not sure what you are using but you > get the idea), then when you are ready, you copy the script over and run > it and it has all the changes. > > Don't make the changes directly to the db, do it all through a script, > then you can just run it anywhere to make the exact same changes. If you > make them directly, that's when it gets to be a pain. > > Travis > > ---- Original Message ---- > From: Christian Watt <[EMAIL PROTECTED]> > Sent: 2001-11-20 08:23:01.0 > To: SQL <[EMAIL PROTECTED]> > Subject: RE: Database Structure Replication > > In theory I am thinking that as long as the structure change will accept > the > data that is already in the fields, you could set up a dts package that > would look at the structure of one DB and possibly copy it another, not > sure > about keeping the data in it. If there is not a lot in your second DB, > you > may just try pushing that data to a temp table while it recreates the > table > with changes, then bring the data back in. I believe that may be the only > way, but try the DTS thing, just make sure that you look at the script > before you run it and make sure that it does not drop the table before > applying changes. If you are successful in doing this, then you can just > run that package anytime you want to make the updates. > > Christian > > -----Original Message----- > From: Bernd VanSkiver [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 19, 2001 3:53 PM > To: SQL > Subject: Database Structure Replication > > > I am using SQL 2000 Enterprise and was wondering if there is a way to > replicate the database structure automatically when I make a change to one > of the databases. I have a test database and a production database, both > have different data but the same structure. Right now if I want to make a > change I have to do it twice, once on the test and once on the production. > Is there a way to replicate the structure and not the data also? if not, > i > can just keep the data synced i guess, but not really what i am wanting to > do. > > Bernd VanSkiver > [EMAIL PROTECTED] > ColdFusion Developer > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
