I'm trying to create an analysis service cube.
The source data for the dimensions etc is coming from tables on a Sql Server 2000 box.
I want to create the cube though on a sql server 2008r2 box.
How do i do this? BIDS seems to want to put the cube in the same place as the data feed? Does that source data have to be on the same server as the cube?
The source data can be located anywhere. The connection string in your data source defines where the data is read from. Set the deployment server in your project properties to tell BIDS where to deploy the cube to.
Related
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.
We are doing a parallel migration of our SQL Server 2005 database, cube and SSIS packages to 2008 R2. The cube successfully migrate to 2008 R2 via the BIDS migration wizard. However, the Data Source View is still pointing to the old server.
Do we need to delete the DSV pointing to the old server, and create a new one pointing to the new server? Or, is there a way to change a property of the DSV so that it uses the new server's data source?
Thanks much for your help and guidance.
The data source view has a "Data Source" property in its property pane which you can see if nothing is selected in the DSV.
And instead of changing this, you can of course just change the connection properties of teh existing data source (note that I really say "data source" here, not "data source view"!).
I have a model created in SSDT (Visual Studio) for SQL Server Analysis Services Tabular. I deployed the model and it works fine.
How can I change the schema of some underlying tables in the model? Some of data types changed and some new columns added in SQL Server tables.
Thanks
If you have made changes in your underlying data source, you can go to the Table Menu -> Table Properties.
This will bring up a window that shows your table and all its columns. There is a check box on each column. If you have added fields, find the fields and make sure the check box is checked. When you click OK, any change in data types should be picked up.