October 31, 2014 at 8:51 am
I am restoring a 3rd party Vendor database from SQL2008R2 Enterprise to SQL2008R2 Standard. I get an error that I can't restore because there is a partition function. When I look at the dependencies it shows a table. When I look at the properties of that table it shows that table is not partitioned. Knowing that partitioning is not supported in Standard and it looks like partitioning is disabled on this table. Could I safely drop the partition function and scheme?
October 31, 2014 at 10:27 am
JeepHound (10/31/2014)
I am restoring a 3rd party Vendor database from SQL2008R2 Enterprise to SQL2008R2 Standard. I get an error that I can't restore because there is a partition function. When I look at the dependencies it shows a table. When I look at the properties of that table it shows that table is not partitioned. Knowing that partitioning is not supported in Standard and it looks like partitioning is disabled on this table. Could I safely drop the partition function and scheme?
Curious.... if you can restore it, how are you able to drop the partition function and scheme?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2014 at 11:09 am
JeepHound (10/31/2014)
I am restoring a 3rd party Vendor database from SQL2008R2 Enterprise to SQL2008R2 Standard. I get an error that I can't restore because there is a partition function. When I look at the dependencies it shows a table. When I look at the properties of that table it shows that table is not partitioned. Knowing that partitioning is not supported in Standard and it looks like partitioning is disabled on this table. Could I safely drop the partition function and scheme?
The partition function(s) and scheme(s) need to be dropped on the originating DB then the backup redone before you can restore the database to a SQL Server 2008 Standard Edition installation. The other choice, if that can't be done on the source system, is to restore the database to Enterprise Edition instance under a different name, drop the partition function(s) and scheme(s), and then do a backup of that database.
October 31, 2014 at 12:01 pm
That is what I was thinking, it seems easy enough. But is there any other reason why removing the function and Scheme would cause problems. This database was originally on a standard edition and upgraded less than a year ago to Enterprise.
October 31, 2014 at 12:06 pm
If the partition function(s) and scheme(s) aren't being used, then there is no reason they couldn't be removed.
October 31, 2014 at 12:08 pm
October 31, 2014 at 12:16 pm
That is a nice DMV I had not idea that existed. Forgive my ignorance, partitioning is a mystery to me. Is there any other way besides dependencies that I can verify if this partition scheme and function are not in use?
October 31, 2014 at 12:20 pm
So I restored to a test enterprise instance and I cannot drop either because they are dependent on a table. THe table does not seem to have partitioning enabled in the properties. Any Idea where I am going wrong here?
November 1, 2014 at 9:54 am
DEfinition of the table and all indexes?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply