Repository Migration Failures

Brian Mellert

Tried to use the Repository Migration Assistant on a simple solution today between our development enviroments.

 

It keeps failing with

The EXECUTE permission was denied on the object 'FragmentStackMapping', database 'e-Work', schema 'dbo'.

 followed by

ExecuteReader requires the command to have a transaction when the connection assigned to the command is in a pending local transaction.  The Transaction property of the command has not been initialized.

 

Our V7 database has always created objects under the eWork user.  The migrator appears to keep dropping and recreating FragmetnStackMapping function as the SA user as dbo.  Even when the DBAs grant access to this function to the eWork user, the migrator appears to drop/create it again meaning the grant disppears.

 

Is the Migration tool written like V9 itself in that is assumes everything, in both databases in this case, is created under dbo. (and owned by SA)?  If so, that is a problem since our V7 has been running under eWork for years.  How do we then migrate data?

Brian Mellert

I got burned by this again while testing from a different database. (Final testing before go live.)
It turns out we had to have the eWork user on the V7 database also be part of the db_owner database role so this temporary procedure would work.