09-20-2011 10:02 AM
Upgrading from 9.01 to 9.10 failed at the database upgrade stage.
SQL Server 2005 Developer SP4 (is on a 1 box test system).
The management and profile database both errored saying they don't support native partitioning.
I have had to go for a clean installation for now and create new databases, which worked ok.
Any reason for the above error?
09-20-2011 12:27 PM
It let's you do a fresh install, so is the upgrade wizard hard coded to only accept Enterprise edition?
09-20-2011 02:34 PM
I guess it checks the edition only. If it's not Enterprise - BSM is not happy. Anyway BSM is not supported on non-Enterprise SQL Server editions.
10-03-2011 07:06 PM
We went through the upgrade in our test 8.07 environment, and it failed on the profile db upgrade. The message was quite random but the only thing I could think of was that our db is SQL 2008 Server R2 Enterprise. I know this isn't supported officially but it was working in 8.07 fine, does it not work at all in 9.1?
03-02-2012 09:54 AM
In our learning environment, I am doing an in-place upgrade with SQL enterprise 2008 sp2 (evaluation edition) and getting the "The following databases DON'T support native partitioning" Do we have to enable native partition somewhere? I believe it is enable by default?
Our BAC 8.07 environment was also on SQL Enterprise 2008 sp2 (evaluation edition) and in the Partitioning and purging manager the enterprise template is activate so BAC recognized our SQL server as Enterprise but BSM does not?
03-04-2012 12:51 PM
He said it should have all functionallity that the real edition have. There is no restriction on the "evaluation edition". I've looked in the pmanager.log and there are partitioning activity (current BAC 8.07) and there doesnt seem to be any error
03-05-2012 08:48 AM
So we were wrong...eval edition was in fact the culprit....as soon as we switch to a a non-eval edition upgrade worked like a charm :)......i wonder what the different is? i consulted several sql forum and they assure me that evaluation edition have full parition capabilities. Maybe it have to do with how bsm detect sql version and does not activate native partitioning unless it is a enterprise edition?
10-25-2012 11:34 AM
Not what I wanted to hear. I'm also having this issue in a fresh 9.20 install...we're using Developer edition in our test environment til we can get a few new boxes built for our Prod environment.
10-25-2012 11:45 AM
SQL Server Developer edition won't work either. I hit this issue myself at one of my customers. BSM was working but data from data collectors were not inserted into DB.
10-25-2012 11:55 AM
Thank you very much. That's exactly what is happening in my test environment right now. I assume once you installed Enterprise & (probably) recreated the databases everything was both hunky and dory?
10-25-2012 07:13 PM
Yep, everything started working fine once SQL Server has been upgraded to Enterprise edition. We didn't even need to recreate any databases.