I have SQL Server 2000 and Analysis Services installed on one VMWare Image. The "MDX Sample Application" can connect to the AS and see all the cubes defined. I clone the VMWare Image to another copy and change the IP. Now, when I open the "MDX Sample Application" in the new VM I cannot see any cube ???
I have also developed a .NET program to run mdx query against the cube, it works when connect to the original VM, but when query against the new VM, I got the following exception
Can not run sql statement "SELECT {[Measures].[Workflow Count]} on COLUMNS FROM [Workflow In Progress]" : Error=>The cube 'Workflow In Progress' does not exist, or it is not processed
Have anyone know how to make MDX Application to see the cubes ???
Check in the new VM if the AS is working properly. Maybe you need execute a re-process in the cube or adjust the metadata to adapt to the new environment. You could make a database's backup in the original VM and a restore in the new VM.
Related
I have none experience with SSAS, I had this cube working perfectly…
The underlying tables that it was using were from a database, let’s call it ‘ABCD’. The problem is, that for other reasons ABCD database had to be split in ‘AB and ‘CD. Half the tables have been migrated to AB and the other half to CD. In my mind I want to open something as ALTER, edit the DB name, and everything would work as before, but SSAS is a bit of a black box for me; can I achieve this?
I know I can just access ABCD and create views to AB and CD and mask my problem, but I would really love to know how to modify the scripts that build the cube….
My recommendation is to just add views into the AB database which point to the tables which have moved to the CD database. Then you can edit the data source from Management Studio and point it to the AB database. (You just connect Object Explorer to Analysis Services, expand down to the database, expand to the Data Source, then double click to edit.)
If that's not an option then you can change the cube source code as follows...
I'm assuming it's a Multidimensional cube, not Tabular. If you already have Visual Studio and SSDT installed, great. Otherwise, install the latest SSDT which runs in Visual Studio 2015 as it's backwards compatible.
In SQL Server Management Studio, connect Object Explorer to Analysis Services and then right click on the database and choose Backup.
In Visual Studio, File... Open... Analysis Services Database. You are editing the cube "source code" live now. As soon as you save a change it will deploy it to the server.
Double click the data source and fix the connection string. Make sure it's using a version of the driver that's on the SSAS server. Point it to the AB database.
Then double click the DSV. In the tables list on the left, right click on each table which was moved to the CD database and choose Replace Table... With New Named Query. Click the "Switch to Generic Query Builder" button and then edit the query to look something like:
select *
from CD.dbo.YourTable
Click Save.
Then go back to Management Studio, right click the database and choose Process. Do a Full Process on the database. It should succeed and be up to date.
It is possible to reverse engineer a deployed SSAS database. The above assumes that's not important to you. But if you need to do this, in Visual Studio do File... New Project... Templates... Business Intelligence... Analysis Services... Import From Server (Multidimensional and Data Mining).
How to create an SSAS server in Multidimensional mode?
I have created an SSAS server using Azure. But it was created in tabular mode. I can't change the mode.
I need a SSAS server in multidimensional mode.
Please help me out.
You provisioned Azure Analysis Services (the one where you connect via asazure://...) but Multidimensional isn't currently supported. Please vote for it.
For other peoples' use in the future... if you created a VM and accidentally installed SSAS In Tabular mode then you can edit msmdsrv.ini and set DeploymentMode to 0 and restart the SSAS Service (kind of the opposite of what Cathy Dumas did here). That will switch the instance to Multidimensional mode.
I have a SQL server reporting service production environment. I need to duplicate this environment on a totally different machine including the source data, let's call it Dev environment. I have backed up and restored both the source database (sourceDataDB) and the report databases (ReportServer and ReportServerTempDB) to this new machine. Re-configured the new reporting service to point to the new report database. Everything works except when I run a report, the report pull out data from the original source database instance instead of the newly created instance. Of course, I can manually modify the data source information from the Report Manager on the new report server. The challenge is every time the ReportServer and ReportServerTempDB got refreshed from the production database, the modified data source got replaced with the one from production environment.
I wonder if there is a way to automate the process of modifying data source information after each database refresh, either from the database end or from the report manager. I only have one data source that is shared with all the reports. This is a SQL Server 2008 R2
Thanks in advance.
I installed Microsoft SQL Analysis Service because I need it to run a forecast analysis from Excel using the Data Mining Plug-in.
When I open MS Management Studio and connect to the SSAS I don't know how to create a new database.
When I right-click over Databases there is nothing like Create Database or New Database.
This is the image of my problem:
Well... I solved my problem reinstalling the suite selecting all of its options.
I still don't know what may cause this problem if not chosen in the instalation options but now I have the New Database option and could finish my job.
Thanks.
I managed to solve this problem by switching Analysis Services from Tabular to Multidimensional mode:
Stop SQL Server Analysis Services service
Go to the config folder, e.g. C:\Program Files\Microsoft SQL Server\MSAS15.SQL2019\OLAP\Config
Copy file msmdsrv.ini to another folder (you can't edit it here directly)
Open the copied file and search for the DeploymentMode xml tag
Set the value to zero
Save the file, copy it back to the Config folder
Start the service
You can use SQL Server Management Studio to create a new, empty database on an instance of SQL Server Analysis Services.
To create an Analysis Services database
Connect to an Analysis Services instance.
In Object Explorer, expand the node for the connected Analysis Services instance.
Right-click the Databases node of the Analysis Services instance and select New Database.
In the New Database dialog box, in Database name, type the name of the new database.
In Impersonation, provide impersonation information for the new database.
In Description, type the optional description for the new database.
Click OK.
I have deployed my SSAS solution to production. On the production server, I want to process my cube, but when I right click on the ssas cube and choose "Process", I recieve the follwong error:
The 'Database' with 'ID' = 'XXX' doesn't exist in the collection.
Has anyone encountered this error in Microsoft SSAS? If so, can anyone tell me what to do to resove this error ?
Check to see what the Id of the database is by right clicking on the database and selecting properties. Check the equivalent in visual studio and confirm it matches. If you have renamed the analysis services project (maybe for a backup), the id of the database does not get renamed and sometimes gets messed up in the XML file.
Try re-processing the dimensions on their own and then the cube. Failing that, if this is the first process (i.e. the cube is not live), try deleting and redeploying from visual studio.
You can re-deploy the OLAP database from SSDT with a different name and before you do you just need to change the database name and set the Processing Option to Full. You can set these options under Project's Configuration Properties->Deployment.
I had the exact same problem. I solved it by editing the roles in my SSAS database :
And then, check the boxes depending on what you want your job to do :
Then, you can process your cubes with your SSIS Jobs.
it can either be roles or kerberos, I got a similar error when the kerberos authentication wasnt setup in the cube server to interact with database server.