SSAS Tabular Model is Deploying in Enterprise version but not in Developer and Standard version

%3CLINGO-SUB%20id%3D%22lingo-sub-1038168%22%20slang%3D%22en-US%22%3ESSAS%20Tabular%20Model%20is%20Deploying%20in%20Enterprise%20version%20but%20not%20in%20Developer%20and%20Standard%20version%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1038168%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3EWe%20were%20using%20SQL%20Server%20Developer%20and%20standard%20edition%20for%20deploying%20the%20tabular%20model%20which%20is%20having%20around%2010%20GB%20of%20data%20but%20suddenly%20it%20started%20showing%20memory%20out%20the%20error.%3CBR%20%2F%3Eearlier%20we%20were%20able%20to%20deploy%20our%20tabular%20model%20using%20both%20editions%20perfectly%20but%20suddenly%20we%20faced%20this%20issue.%3CBR%20%2F%3Ewhen%20we%20explored%20more%20we%20found%20many%20solutions%20like%20to%20reset%20vertipaq%20page%20limit%2C%20memory%20limits%2C%20closing%20all%20running%20apps%2C%20rebooting%20the%20system%20but%20nothing%20worked.%3CBR%20%2F%3Ewhen%20we%20did%20more%20research%20then%20we%20come%20to%20know%20that%20SQL%20server%20developer%20and%20standard%20edition%20can%20use%20max%2016GB%20or%20RAM%20for%20tabular%20model%20whereas%20SQL%20Server%20can%20use%20a%20maximum%20of%20OS%20so%20we%20decided%20to%20test%20with%20Enterprise%20Edition%20and%20when%20we%20tested%20we%20got%20100%25%20results.%20we%20have%20tried%20many%20times%20each%20time%20our%20model%20gets%20deployed.%3CBR%20%2F%3Ewe%20have%20discussed%20the%20issue%20with%20other%20senior%20SQL%20consultants%20they%20suggested%20us%20that%20the%20issue%20which%20we%20were%20facing%20was%20not%20due%20to%20SQL%20Server%20editions.%20it%20may%20be%20a%20bug.%3CBR%20%2F%3ECan%20you%20please%20clarify%3F%20Is%20this%20due%20to%20SQL%20upgrade%20or%20it%20is%20actually%20a%20technical%20bug%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hi All,

We were using SQL Server Developer and standard edition for deploying the tabular model which is having around 10 GB of data but suddenly it started showing memory out the error.
earlier we were able to deploy our tabular model using both editions perfectly but suddenly we faced this issue.
when we explored more we found many solutions like to reset vertipaq page limit, memory limits, closing all running apps, rebooting the system but nothing worked.
when we did more research then we come to know that SQL server developer and standard edition can use max 16GB or RAM for tabular model whereas SQL Server can use a maximum of OS so we decided to test with Enterprise Edition and when we tested we got 100% results. we have tried many times each time our model gets deployed.
we have discussed the issue with other senior SQL consultants they suggested us that the issue which we were facing was not due to SQL Server editions. it may be a bug.
Can you please clarify? Is this due to SQL upgrade or it is actually a technical bug?

 

0 Replies