On Nov 22, 8:33 pm, Dave <D...> wrote:
> "kchieff" wrote:
> > It's unlikely that you'll be able to revert your data back to BCM 2007
> > if you choose not to move ahead - I would not move my production
> > database to 2010, I would copy it and try it, knowing that I may lose
> > any changes that I made should I decide not to move everyone to 2010.
>
> > On Thu, 19 Nov 2009 01:28:08 -0800 (PST), Sun Embraser
> > <sunembraser2...@hotmail.com> wrote:
>
> > >On Nov 18, 9:03 am, Dave <D...> wrote:
> > >> I can't find any information on if a BCM 2010 client can access a shared
> > >> database created by the BCM 2007 shared database tool. Our how the migration
> > >> process will work for people moving from BCM 2007 to BCM 2010.
>
> > >> Thanks
>
> > >Hi, after installing BCM 2010, existing BCM 2007 database (running in
> > >SQL Server 2005 Express) will be migrated to SQL Server 2008 Express
> > >automatically.
> > >From that point on, all shared clients will need to be using BCM 2010
> > >to connect to that database... meaning you will want to upgrade all of
> > >your shared environment to Office 2010 + BCM 2010 if you choose to use
> > >Office 2010.
> > >Of course, before upgrading, backing up your data (either through
> > >"Backup" or "Export") is strongly recommended.
> > >Thanks,
> > >John
> > .
> OK I just saw the post with the tool and it says you can backup and restore
> your 2007 db to a sql 2k8 server so I'll give it a try and see how it goes.
> Thanks-
kchieff is right. There is no option in BCM 2010 to let you go back
to the 2007 database format once you move forward. Back up data is a
good idea. Use a test environment is also a good idea, if you can
affort the extra hardware or have virtual machines for this.
Dave, please do let us know if your experiement works out. I saw the
same post too, and they say BCM 2010 works with SQL 2005. I guess if
you have SQL Express 2005, upgrading to SQL Express 2008 should be a
good idea, but if you have any other version of SQL 2005 (that you
paid for), the BCM team is thoughtful enough to not force you to
upgrade to SQL Express 2008 - that you can keep using SQL 2005.
John