Upsize to SQL 2008 hanging at t_document

[AndyR]

Hi all,
Am trying to upsize our central EAP file to a DBMS SQL Server 2008 database but the transfer keeps hanging.
I have created a new database on a 2008 SQL Server, ran the easchema.sql script to create the tables, and give my user account full access including the db_ddladmin permission.  I have done the integrity check of the database which is OK and when I connect to the database ready to do the transfer it tests OK.
When I start the transfer it runs fine till it gets to copying project information for: t_document and just sits there.  The sql mdb file always gets to 37,888kb and no higher but its not a space issue as there is plenty of space on the server.

I've left it for an hour now and its not moved.  I've tried killing the transfer and repeating but no luck, always hangs at the same point.  If I browse the sql database and look at tables which have completed I can see data, but nothing in the dbo.t_document table so its not even starting.  The log file just shows it starting t_document but thats it.

We are using EA 9.1 Corporate Edition.

Any ideas?

Andy

[qwerty]

Try the following:
- run a model consistency check prior to the transfer
- try a transfer to somewhere else
- use xml ex-/import
- contact Sparx support

q.

[Geert Bellekens]

Andy,

How large is your .eap file (after compacting)?
Do you use baselines a lot? Because the t_document table contains (amongs other things) the baselines in a zipped binary field.

XMI export/import into a fresh model would get rid of those I guess, but if you have a large model (50 MB+) that might take even longer then trying to transfer.

Another thing, have you checked the allowed size of the database in SQL Server? I know there are some settings that control the size (and autogrow) of the database.

Have you tried to leave the process running overnight? (long shot, I know)

Last resort is to clean out the t_document table yourself (after taking a backup of course)

Geert

[hd]

Remove replication if the eap file is part of a replica set.

[AndyR]

Thanks guys, we have sorted it now.

For reference the EAP was 220mb and then 190mb after compress.

Initially I didn't think there was a replica but turns out one user did have a replica set with auto sync too.  We tried removing this but no matter what we did we couldn't get it removed, so I used the transfer tool to go EAP to EAP and created a new EAP file from that.  I then tried the import of this and it worked first time so looks like it was a replication problem.  Not sure why we couldn't remove but no worries, its working now.

Thanks for the help,

Andy