Hi,

I have a same problem

I had create 2 new triggers and try to Deploy it to SQL Server database.

THen during deployment I'v got an error



An error occurred while deploying the meta data to the server

ArgumentException

Spalte tr_Schema gehoert nicht zu Tabelle DBETriggers.

Source : System.Data

Stack Trace:

bei System.Data.DataRow.GetDataColumn(String columnName)

bei System.Data.DataRow.Get_Item(String columnName)

bei MicroFour.StrataFrame.DBEngine.SQL.TriggerInfo.get_tr_Schema()

bei MicroFour.StrataFrame.DBEngine.SQL.DatabaseMigrator.CreateTrigger(Table triggerParent, TriggerInfo info)

bei MicroFour.StrataFrame.DBEngine.DatabaseMIgrator.EnsureTriggers(Table triggerParent, TableInfo tblInfo)

bei MicroFour.StrataFrame.DBEngine.DatabaseMIgrator.EnsureTriggers(Database Db, DatabaseInfo DbInfo)

bei MicroFour.StrataFrame.DBEngine.DatabaseMIgrator.EnsureDatabases()

bei MicroFour.StrataFrame.DBEngine.DatabaseMIgrator.DeployMetaDataThread()

This has recently become an issue for me as well. Some info that may or may not help... At one point we set the collation to be case insensitive which had all sorts of problems on the deployed database. One of the biggest items I noticed was that triggers could not be enabled/disabled. I've switched it back, added a new field to a table and assigned it as the primary key, int, auto increment after making the original pk on that table a regular field. Not sure much else has changed but now I'm getting this error.

Is there an official response on this? Could it possibly be fixed by somehow resetting the whole database back to square 1? Meaning that it would just create the database as is without going through any additional scripting to make all the incremental changes that have happened? This would only work for me because I have'nt officially locked in our schema anywhere yet. If I were into it then I'd need another fix.

My thought is... "Could it have something to do with incremental changes that have somehow confused the deployment?"

Matt

Actually, that is a bit strange.  The tr_Schema was a temporary field that was in the DDT a long time ago and is no longer used.  It seems like you may have an older package.  Regardless, we are posting a pre-release build (1.7.3.4) in the My Account area here in just a bit.  There have been a lot of fixes and this should make sure that this doesn't crop up.  This is ringing a bell and looking back at some of the fixes, I think that this update will resolve your issue.

We have been running and releasing this build, so it is fully supported and stable.  We will make this more official in the weeks to come.