Strictly a MySQL Question

kklosson

I promise to read a good book on MySQL but I have one question right now. I am deploying my application to an external server for testing. My test bed and server are both running MySQL. I thought I could put my current test data on the server by copying the files data directory from my development machine to the server, then copy the files from the basdbtest folder on the server to the basdb folder on the server. That didn't work out and I was ultimately unable to load my .bsv or log in to the system. I will probably just reinstall AwareIM and start over with the database.

Was I crazy to try that?

thom

kklosson,

"There is a fine line between crazy and genius...."

I have moved my test data several several times onto my production server(although on SQL Server Express), and will share some thoughts

First, I know MySQL loves the command line, but there are several good GUI MySQLAdmin tools available. I highly recommend these with your choice book.

Second, Aware has IMPORT/EXPORT functions - you can write some batch processes that will dump or export from test and import into basdb

Third, if you are familar with SQL statements, then you can create a linked server in MySQL (you'll have to look up the syntax to do that for the command line) this will allow you to perform some straight forward SQL statements to move your database from the basdbtestdomain.tables to the basdb.tables (basically a INSERT INTO basdb..bsv_tablename SELECT * FROM basdbtest..bastestdomainbsv_tablename ). I have notice that on some tables the column order does not match up from basdbtest to basdb - some you will need to specify column names in the SELECT and INSERT clauses). There are some AwareIM system or control tables like BAS_IDGEN - that generate key values. You'll want to be very carefull that none of your BO.ID values from test are greater than the MAX_KEY - this will cause unique contrainst errors ( in general, I would be shocked if Aware Support did not discourage this method).

I hope this helps

aware_support

There is some very old but very good thread on how to copy data from MySQL (from memory the thread is from greg) - if you find it we'll move it to Tips and Tricks. It explains the principles of the process - which tables to copy and in which order. The SQL Server and Oracle would be similar to MySQL

Copying data from Derby can only be done using export/import at the moment. Copying the DATA folder from one machine to the other IS NOT ALLOWED - it shouldn't be used.

If you can use third party tools for Derby to backup and restore database tables you should apply the same principles.

kklosson

Thank you - I'll look for that but most of what you said I have learned the hard way. I ended up starting over for my limited testing which is probably best since I immediately discovered some basic errors in initialization issues.