Click here to Skip to main content
16,005,734 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Need to be able to take certain data rows that are application configuration information and package them together as a set and then migrate the set from development to test to staging to production. largely I am interested in migrating database table rows together. For example, I have some mailing addresses, phone numbers and other information that I need to publish to web pages, reports, and letters. I manage these as configuration data that need to go together. no preference on the language, .NET, Java, etc. just need it to be web deployed.

What I have tried:

tried coding some of this from scratch but there must be solutions that do most of this.
Posted
Updated 20-Apr-20 16:58pm
Comments
CHill60 20-Apr-20 17:00pm    
Where are these "data rows" stored?
bruce baur 20-Apr-20 23:42pm    
the data rows are in SQL Server tables for the most part. so I am looking to create a simple tool that allows me to manage changes to certain ones and group those changes to allow for them to be deployed and "migrated" to the next environment.

1 solution

As CHill60 has asked, 'where are these 'data rows' stored?

Depending on the amount(s) of data, and the data source, could you drop the data as xml files ? MS SQLServer 'bcp' can output to and load from XML files

bcp Utility - SQL Server | Microsoft Docs[^]
 
Share this answer
 
Comments
bruce baur 21-Apr-20 8:27am    
Yes the data rows could be dropped as xml. the main thing I am hunting is a management tool that allows me to designate and package various rows in a "package" for migration. an easy to use interface that end users can modify values, and target them for deployment. for example, as mentioned above, say the customer maintains things such as return addresses to be printed on all their letters. this return address could be maintained and selected for migration. There are many pieces of configuration data to maintain so having a tool like this would make it easy on them.
Garth J Lancaster 21-Apr-20 9:18am    
the input to bcp is SQL - so, how about a script - DOS, Powershell, that you can run as part of your build process, that has the SQL statements required to select your data and create the file(s) - that way the script is an artefact/part of the build process

I'm sure there are lots of (complex) ways of achieving your goal, I'm just suggesting a KISS approach with easily available tools

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900