March 6, 2017 at 1:16 pm
Hello, I had VS13, long story but it went corrupt, and any package you tried to open it would corrupt. It was used to create and deploy many SSIS and SSAS packages and models. So I installed VS15 Community with SSDT 14. The VS13 gave the options and selections on the solution to make the cube an In-Memory for example. VS15 doesn't. Is VS15 configurable to do so? Or is it not compatible at all? Thanks, JPQ
March 7, 2017 at 9:22 am
As I continue to trouble shoot this, here are more odd things uncovered.
I can open VS15C/SSDT on my local PC and import a model from prod and check and see the props on the model are in-memory, as well as the workspace model it creates is also in-memory.
I do this same thing but on the server, and it is not a in-memory model, and that's placing it into a free standing project, as well as letting TFS VC the newly extracted project.
Seems that anything model wise performed on the server and it's not importing as a in-memory model.
How very odd. How can one deploy a cube as in-memory like this?
March 7, 2017 at 9:49 am
If I call up a previous imported cube model from production, that will be in a SQL Server 2014 SSAS format, and use the VS15C/SSDT tool to convert it to 1200, as warned to do as as it says its incompatible, then it will convert it, and that's when it's no longer an in-memory cube. What is up with that?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply