Re: [xwiki-users] Problem Migrating Database from XWiki Ent 3.5.1 to 4.1.3 for MSSQL

Hi, You do not need to enable additional logging if you are using our default configuration. If currently you do not get an info logging saying "Running storage schema updates and migrations" at some point, and your database is declared "Database XXX needs migration(s), it could not be safely used!", it simply means that you have not enable migration. Migration are disabled by default, and, in our distributions, we active them initially by having the following line uncommented in xwiki.cfg: xwiki.store.migration=1 Reading the xwiki.cfg you have pasted, I do not see that one, so you have to add it back. Apart from that, you just need that the store and migration components are properly setup, which is the default, and the subject of my previous message. Regarding schema changes, you are right, all changes concern the size of IDs in many tables (the changes depends on the source DB), to afford a 64bits number for all documents and objects IDs. If you compare the hibernate mapping, this is what you will see. But, on an existing database, you need a migration procedure that will alter the existing ID columns to change their type. To do so, most DB engines will also require that no contraints are exists on these columns, so we potentially need to remove them first and recreate them later. And the last but not the least, we also migrate all IDs to use the new size and scheme, which will ensure better unique identification, our goal in this operation. On Thu, Aug 2, 2012 at 10:17 PM, rheim651 <rob.heim(a)mckesson.com> wrote: -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO