Sunday, December 30, 2012 1:29 PM
I am trying to implement a warehouse database in SSDT. The database itself was managed classic previously. (It was not a Data Dude project.) I reverse engineer the database into an SSDT project and - sure enough - there is a storage folder with my partition function, scheme, and filegroup entries. Great. But I try and build it to localdb and I get the below two messages. What am I doing wrong?Error 1 SQL72014: .Net SqlClient Data Provider: Msg 7736, Level 16, State 1, Line 2 Partition function can only be created in Enterprise edition of SQL Server. Only Enterprise edition of SQL Server supports partitioning. C:\Users\jflannery\Projects\BI\Warehouse\bin\Debug\Warehouse.sql 48 1 Warehouse
Error 2 SQL72045: Script execution error. The executed script:
CREATE PARTITION FUNCTION [pfQuarterly](INT)
FOR VALUES (20100331, 20100630, 20100930, 20101231, 20110331, 20110630, 20110930, 20111231, 20120331, 20120630, 20120930, 20121231, 20130331, 20130630, 20130930, 20131231);
C:\Users\jflannery\Projects\BI\Warehouse\bin\Debug\Warehouse.sql 47 0 Warehouse
Sunday, December 30, 2012 5:59 PM
Error 1 SQL72014: .Net SqlClient Data Provider: Msg 7736, Level 16, State 1, Line 2 Partition function can only be created in Enterprise edition of SQL Server. Only Enterprise edition of SQL Server supports partitioning.
is the error message not precise enough ?
table partitioning is only availabe in SQL Server Enterprise Edition (and SQL Server Developer Edition for developing) and in no other edition.
localdb is more like SQL Express and therefore does not included partitioning.
What you can do ?
buy SQL Server Enterprise edition.
if you're a developer with a MSDN subscription you can usually install SQL Server Developer edition and develop & test your code on your local computer but when you want to deploy your solution to production environment you need SQL Server Enterprise edition.
Alternatively you can drop the partitioning in your SSDT project and than it may be compatible with your localdb as long as the size does not exceed the capacity of locadb and you're not using any features not supported on localdb.
Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful.