This might fit better over at StackOverflow, but I'll throw in my two cents.
This is part of the application deployment process that you'll need to figure out. You need to take a look at the database schema on the production server and the schema on the test server and then figure out exactly what changes are required to make them match. You'll have to go through table-by-table, column-by-column. Depending on the changes required, it's possible that you can't do a non-destructive deployment. Some changes are invasive enough that the only option is to migrate the data (sometimes this means exporting and reloading it, possibly with some data manipulation in between, but hopefully it means creating a replacement table in the production database and using SQL to dump the contents of the old table into it (possibly with some manipulation)).
In the future, I would recommend keeping database changes prominently in mind during the development process. Always remember that you're going to have to get those changes into the production server, and if you track your changes as you make them and plan out how they're going to be deployed, you can mak the deployment a lot easier.