MySql Dataset functionality reduce after moving from dev to godaddy mysql server

Noticed reduced functionality on mysql dataset on vs2010 after moving the db to the development server.  Then trying to create a dataset.  The dataset no longer showed references. Is there a way to solve this so that the referential integrity exists between tables when dropping respective tables onto the dataset design surface using a db on the's mysql data store?

The image attached shows that referential integrity was fine if the mysql db is on the development system. But after moving the db to the go daddy system, the db no longer showed referential integrity after dropping tables on the design surface of the dataset.

Who is Participating?
Guy Hengel [angelIII / a3]Connect With a Mentor Billing EngineerCommented:
either, you did not migrate the foreign key stuff to the dev server, or the dev server does not have the InnoDb engine activated, for example.
mnnoonAuthor Commented:
Do you think I should export the database instead of using the query window, or does it really matter?  As far as in the options disabled section in the help, it doesn't mention anything about whether the InnoDB engine has be deactivated or not.
Relevent Articles Below
Exporting versus using the SQL Query windows:
Options disabled in hosted accounts:
mnnoonAuthor Commented:
I didn't understand this answer, but it makes sense.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.