I need to add a new version of a Cube in an existing SSAS database. I've created the new Cube by using Management Studio to script the old Cube to a screen, changed the ID's to the new ID, and executing the script.
So now the new Cube exists in the database.
I want to put the new cube into my existing Visual Studio project. Can I import a cube from a database (as opposed to the whole database)? Can I import the script logic that is created by Management Studio?
If neither of these things, what is the best way for me to import this new cube into the project?
Thanks, --sw
ps--all versions are the newest (e.g., Visual Studio 2012, SSAS 2012, and so on). --sw
I would start from a Visual Studio Project, which is the "source code" for SSAS. If you dont have this already you can use Visual Studio to Import from the server, while creating a new Project.
Then in Visual Studio I would copy and paste the Cube object, and work from there.
Related
VS2017, Click "Create Report in Microsoft Excel", Excel 2016 opens, once I click Finish, throws this
"TF208071: The following error occurred when the command was generating PivotTable and PivotChart reports. Close the Microsoft Excel workbook and try again, or press F1 for more information.
Object reference not set to an instance of an object.
"
Recently upgraded TFS server to 2017, I can still generate the reports using Visual Studio 2012/2013 by connecting to the same TFS server. However not on VS2017.
Where do I start looking? None of the event logs show any such error.
I have 4 columns of data from the WI to export, so its not the amount of data.
Seems you are talking about create Excel reports from a work item query, try to clear TFS and VS cache and test again.
Besides, since you are using TFS2017 and VS2017, you could try to use this extension--VSTS Open in Excel, you could use this extension for bulk editing work items, or to leverage Excel tools to analyze and visualize a large number of work items. You could directly open work items in web portal.
Besides, as a workaround, you could still generate the reports using Visual Studio 2012/2013 by connecting to the same TFS server.
Hope it helps someone!
The issue is with the 2017 TFS COM Add-in, this has an issue used with Excel 2016. seems like a bug from Microsoft!
So we removed all the TFS addin from Excel2016. Then do a repair install of 2015 Office integration which will set V14 Com Add-in to load at start. Then it will export through VS2017 (using the 2015 COM IN)
You can also edit this through regedit, make the V14 OR V13 COM Add-in to load at startup by editing that specific TFS Addin to a value of 3 and setting all the rest to 0.
I'm working with Visual Studio 2012 and ODAC 1120320.
In this project I need 2 different edmx files since I've to work with 2 different DBs.
But I managed to import table only from the first schema, when I try with the second the Entity Data Model Wizard stops working and stays in Not Responding status for hours.
Can you help me to understand what is wrong?
I have my Visual Studio C# source code inside Microsoft Azure - Visual Studio Online (VSO), which is basically Team Foundation Server (TFS) 2013 in a Cloud. The Project was created using Microsoft Visual Studio Scrum 2013.3 Process Template.
I need to change process template from current (Scrum) to native Microsoft Visual Studio Agile 2013.3 Process Template.
Currently I do have only source code inside VSO and need to preserve all versions/check ins, with date/times and owners for whole team, there are NO any work items (tasks, bugs etc.)
One solution is to open a new Project inside VSO with Agile template, however how to migrate my code? or how to make simple / easy changes to current VSO project to change process template?
Create a new project and branch your code to the new project. The old project must remain to maintain history
use the TFS Integration tools to replay history against the new location.
(recommended) Switch to Git and use Git-TF to pull the history into git.
check out the tip and check into the new project.
The only option here that adds future value is to move to Git. Once there your history will be forever portable.
Sometime opening my solution, the database project is disabled and marked as need migration as below snapshot.
I don't know how to deal with that. What should I do to unlock it?
It sounds like your database project is in the old VS 2010 format, as opposed to the new SQL Server Data Tools format.
In that case you'll need to upgrade the project. There should be an upgrade option if you right-click the project in Solution Explorer.
In Visual Studio versions prior to 2012 you could open the Data Source tool window, click the add data source button select object and navigate the project namespace hierarchy to a class (business object). Visual Studio 2012, out of the box, doesn't allow you to simply select a class anymore. My question is how do I add a data source based on a business object to my project in Visual Studio 2012 or how do I revert to the old functionality?
I've fixed the issue by right clicking on the solution and choosing clean and rebuilding everything. I'm now able to create a data source as described in my question.