Saturday, February 04, 2012 ..:: Forums ::.. Register  Login
 Forums Minimize
 
ForumForumMainstream Foru...Mainstream Foru...Best PracticesBest PracticesMigrating Code and Configuration ChangesMigrating Code and Configuration Changes
Previous Previous
 
Next Next
New Post
 8/6/2008 8:35 AM
 

I am looking for any advice people may have in supporting a Splendid environment.  I have a development, test, and production environments.  Are there any best practices for migrating code changes, configuration changes, etc. from one environment to the other, and keeping them in sync?  I am specifically concerned about configuration changes.  For example, if I add custom fields on my development machine, is there an accepted way to dump those changes (which should be in SQL tables) and load that data safely in the test environment? 

Thank you,

Brian

New Post
 8/6/2008 10:39 AM
 

When we expect to duplicate schema changes, we always code them in SQL.

if not exists(select * from sysobjects inner join syscolumns on syscolumns.id = sysobjects.id where sysobjects.name = 'LEADS_CSTM' and syscolumns.name = 'TIME_FRAME_C')
  begin -- then
 print 'Adding LEADS_CSTM.TIME_FRAME_C'
 
 exec dbo.spFIELDS_META_DATA_Insert null, null, 'TIME_FRAME', 'Time frame for move in', 'TIME_FRAME', 'Leads', 'varchar', 25, 0, 0, null, null, 0;
  end -- if;

Previous Previous
 
Next Next
ForumForumMainstream Foru...Mainstream Foru...Best PracticesBest PracticesMigrating Code and Configuration ChangesMigrating Code and Configuration Changes


  
Copyright (c) 2006-2010 SplendidCRM Software, Inc. All Rights Reserved.   Terms Of Use  Privacy Statement
DotNetNuke® is copyright 2002-2012 by DotNetNuke Corporation