For those database administrators who have to deal with such a Dynamics Ax 2009 and his henchmen (developers, consultants, etc. 
) I leave here a couple of things you should know (or I should say) when we join ax2009 and sql server 2008. Sometimes you can point to the database as a source of the problem but not always. Some requirements to consider for installing Ax2009 are that the user you want access to the system should be user and DOMAIN in sql server role must be a member of securityadmin dbcreator and to create the new database from Ax installer. Once installed (or during the installation process) the problem with the database that we can find include:
Case 1:
Another known problem in data synchronization can be caused by the lack of permits. The message goes like this:
"Cannot execute a data definition language command on ().
The SQL database has issued an error.
Problems during SQL data dictionary synchronization.
The operation failed.
Synchronize failed on 1 table(s)"
This particular case is solved giving db_ddladmin permissions on the database in question. According to the official document setup Dynamics Ax 2009 AOS user must have the roles db_ddladmin, db_datareader, and db_datawriter on your database-enabled everything work properly.
Case 2:
Ax2009 may be that in adding a field on a table can not be reflected in the database but in the AOT
Axapta. If it is something that occurs only in the field, or rather with that type of field (Extended Data Type) database has nothing to do. The problem is probably that the functionality of hanging this type of field is disabled. This usually happens at a new facility which has not been activated at all (Thanks Alexander for the help! 
).
In another post I hope to discuss what steps to follow when you synchronize a table Ax.
