Synch 2 tables with different names

[secureconect101]

Maybe there is a better way to handle this but I currently have both a staging and production set of tables which live in one DB. Since many shared hosting environments only provide the use of one DB I have accomidated this by having staging_%tbl_name% and prod_%tbl_name%. But as I move from staging to production as well as bringing production data, after time back to staging for further development. I am not able to use any of the sych tools because though the data and structure is exactly the same the names are not.

Any suggestions?

[peterlaursen]

Not really any other suggestion than getting access to another DB or even another server.

SJA won't sync two tables on the same DB with different names, as you have noticed yourself.

You don't have a MySQL server running on your local machine? That would be the one solution to have it.

With this solution you could sync staging_%tbl_name% from your webhosting to localhost, rename staging_%tbl_name% to prod_%tbl_name% on localhost and sync prod_%tbl_name% from localhost to your webhost – with the result that staging_%tbl_name% will be sync'ed with prod_%tbl_name%

Personally I would prefer running the development or “staging” -database on localhost at least in early stages of development. But of course that would probably involve a complete setup of a webserver, a preprocessor (PHP or ASP most likely) and and MySQL server on your local. However it is not very complicated to set up (at least not Apache + PHP + Mysql).

If you only wnat to install MySQL on your local it will install and cofigure itself in a few minutes … Of course there are a lot of optimizations that could be done afterwards, but with this simple need you won't have to do any of that stuff…

[secureconect101]

Thanks,

Yes. I understand what you are saying and yes I already have local copies and DB's running. That I consider my Dev version. Both Staging and Production are for the Client. Staging is the Near Live Version. This allows me to demo newly released function prior to live on the same base code and enviornment. As well as it give the client the ability to test out stuff without effecting the live site.

In CMS and E-Comm env's I don't like working on the live Data till all is 100%

In a corporate enviornment you would have 3 servers… tring to bring a little of that to my product and customers.

Thanks For your help. I knew it was a long shot but just wanted to be sure.

[peterlaursen]

your are welcome … but I really am not sure if it was any help!

[Author]

Posts