Processing Cube Dimension Incrementally

I didn't find much about how to process dimensions incrementally in a cube. To be clear, I am focusing on processing cube dimensions not dimension table. I have seen and work with different setting of the cube and work with "Process Update".

This process the data incrementally in the Cube dimensions.

If you using SSIS drag and drop analysis service item and set the setting as "Process Update".

sqlmanagment studio: cannot find one or more components. Please reinstall the application

 

This can 

(after installing vs2013)

SSMS Depends on Visual Studio 2010 IDE, which if not installed the SQL Server Setup will do, but if any version is present, the setup will ignore it, even at repair

Re Install, I figured that the SSMS needs Visual Studio 10 IDE to run, which I've removed by mistake after uninstalling VS 2010.

So, I Opened the Setup Media and searched for Visual Studio Setup. The .msi file run quitly and Filled the missing parts, and the Management Studio Run OK.

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/3dd6f643-720f-4878-9594-894da73efd46/sqlmanagment-studio-cannot-find-one-or-more-components-please-reinstall-the-application-after?referrer=http://social.msdn.microsoft.com/Forums/sqlserver/en-US/3dd6f643-720f-4878-9594-894da73efd46/sqlmanagment-studio-cannot-find-one-or-more-components-please-reinstall-the-application-after?forum=sqlexpress 

I found that if you do not have the CD you can get the VS 2010 IDE component that SSMS 2012 relies on here:

http://www.microsoft.com/en-us/download/confirmation.aspx?id=1366

It's called Microsoft Visual Studio 2010 Shell (Isolated)

After installing that, SSMS runs for me again, Microsoft needs to add this install into their repair logic!

System.Runtime.InteropServices.COMException (0x800A03EC): Microsoft Excel cannot access the file

I develop a package in SSIS, I need to use format excel sheets and I am sure many of you will using it because of business people needing data in pretty form. Any ways, till this part when I run from SSIS it works like a champ. But as soon as I scheduled in SQL agent on server it started to fail with below error.

Description: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException (0x800A03EC): Microsoft Excel cannot access the file 'xxxxxlsx'. There are several possible reasons:    ? The file name or path does not exist.  ? The file is being used by another program.  ? The workbook you are trying to save has the same name as a currently open workbook.     at Microsoft.Office.Interop.Excel.Workbooks


After sometime when I was about to give up because the solutions I was seeing on the web either say go play with DcomConfig or hack registry keys yeah like some one is gonna let me do that on prod server.

Finally found MS document that hints the below procedure it works and best part don't need to mess with registry keys.

Solution(1)

Create folder called "Desktop" really dont know why but it works.

Create directory "C:\Windows\SysWOW64\config\systemprofile\Desktop” (for 64 bit Windows) or "C:\Windows\System32\config\systemprofile\Desktop” (for 32 bit Windows)

In my case I had created folder on both locations and give read write permissions on it

P.S

You will still see this error even if you have created the folder but the permissions are not correct.

Cache InterSystems Database And SSIS

This Post is important as I got an experienced with Cache Intersystems Database and SSIS.  Most of you who don't know about Cache database, this is not relational database. This Database is based on classes and objects and it reside in memory.

CACHE DB CONNECTION :

Cache DB is connected with ODBC connection only. You will find ODBC connection in ADO.NET component.

In my Case Tables were not loading into the SSIS. And I had no clue what are the table names so I have to use SQL command. If you are also in this situation then you can use Access DB it uses an easy way to connect and load to ODBC and it can show you all the tables. Another way is to use SSMS and use link serves to get to the ODBC. I personally would prefer to use Access because of easiness.

Follow the screen shots and once you setup the connection for Cache database in SSIS, Right click the ADO component and select properties and Set the connection manager.

This is should fix the Cache and other ODBC connections to SSIS.