I've been having an error after I added some partitions (year related) to my cube. I added the partitions on partition manager at SSAS (Visual Studio) and then copied the final code of the cube and created it in SSMS. I dont even have data there yet but I am already experiencing errors in the fact table. There are some specific METRICS that is giving me an error after adding the partitions but it doesnt even say what. Have you guys ever experienced something like this? thanks in advance.
Related
I'm still new to SSAS cubes and came across a very interesting thing. When I deploy me cube to the server and browse it and compare the results to the temp Cube that's created by default. I get different results.
Can you please explain why this is happening and the way forward.
Thank you
I ran into an issue last night that I cannot quite figure out. I'm no SQL expert and after doing countless google searches I'm still nowhere close to figuring out why this is happening.
About six weeks ago a table was supposedly dropped from my database, not by me. After this table was dropped all the views that depended on it still functioned properly. This table was unused but still had a handful of dependencies as I can see now in the Object Dependency viewer in SQL Management Studio. We implemented a few updates to out SQL Server 2012 last night and the server was restarted.
At about the time these updates were going on we started to receive a bunch of errors all revolving around this missing table that was deleted 6 weeks ago. After recreating the table everything was fine.
We're currently going through the updates to see if they could have effected it in any way. Does anyone know if there is any sort of caching that could have been going on that I'm not aware of? I'm really stumped as to why this worked for those 6 weeks.
Was the table a temp table? (A table name preceded by #.) If so, SQL sometimes caches temp tables. That could explain why the views worked. Then, when you updated your server and restarted it, the temp table caching was cleared.
I am a beginner level programmer who was assigned to update the data content in UI. this UI references a database table so I went ahead and began updating the table as per constraints. I had a backup of the data taken and had the create construct imported as well before running the modification queries on SQL Server Management Studio 2008.
A misleading update statement corrupted the table when it updated the whole database instead of 4 rows and I could not pin point to what data ended up being modified and what remained same. Long story short, I had to delete the records and eventually drop the table and then reconstruct it also. Everything went well, I recreated the schema and inserted the data from the backup and continued querying.
However, the UI which was populating its display section from my table went all blank after the incident and I am at a loss to know where is it exactly that I went wrong. It is a small database and this table was NOT referencing any other table. The permissions look good as it was before. I can't really understand what has gone wrong. Queries work well.
If you have had the patience to read my tediously long narrative till now, can you please tell me what is it that I am missing here ?!
I apologize for the overdrawn description but the context felt more important than the problem statement itself.
I have performed ETL operation and i created a data warehouse and i loaded the data to it and so far its fine.. my ETL seems to work allright since my data warehouse contains all the data i needed. And then i created an SSAS project from my data warehouse following the AdventureWorks DW example. I deployed the cube and processed it. Then i tried to browse the cube. But here is a problem, it seems as the members do exist but the measures are empty. because my dimensions contain the data but when i throw the measures to it .. it is just gonna be empty cells. What causes this?
In the cube designer, check the "Dimension Usage" tab. Make sure that the intersection between a dimension and a measure group has something there (If there's meant to be a relation).
What happens if you drag & drop the measure to the browser, without any dimensions?
Also what version of SSAS are you on, is it 2005? That had IgnoreUnrelatedDimensions set differently to 2008 I think..
Make sure you've linked your dimensions with measure groups (i.e. that you fact table references you dimension tables).
Also make sure you have foreign keys defined in your data warehouse (as soon as wizards in Visual Studio use them when proposing cube structure).
In order to deploy to a different dwh server
Right Click on the CubeNAME
Go to properties
In Configuration properties > Go to Deployment
In Processing option - change Default to - Do not Process.
if in case the DB is very large and keep huge data, it will get deployed and you can process it later.
For Target - Set name of Server
Click on OK, Deploy and later process
I'm trying to configure storage mode ROLAP for a partition in an existing SSAS cube. The cube is a little messy in that the measure group is defined by a named query (as opposed to a table) and the dimensions are defined in several different data source views (DSV).
This is the error message I get when querying the cube with mdx:
Executing the query ...
Server: The operation has been cancelled.
Errors in the high-level relational engine. The 'dbo_dim_account' table that is required for a join cannot be reached based on the relationships in the data source view.
Execution complete
Note that MOLAP storage mode with proactive caching works fine. This problem occurs only when storage mode is ROLAP or HOLAP.
Also, I have tried to add the tables of all dimensions to the DSV of the cube in question but that doesn't seem to help.
Any ideas?
Not an expert here, but you could try importing the AS DB in Visual Studio.NET - "Import Analysis Services database" in the New Project... dialog.
Once in there, you can see the table schemas for the Data Source View (which is where the relational tables are defined that the cubes are extracted from). Next, look to make sure the "dbo_dim_account" table is there and that your fact table is related to it.
It may be that a dimension and fact have to be in the same DSV for the relation to work?
Also, maybe the SSAS flight recorder or Application log would have more issues?