Jul 15

If you’ve not heard of Gemini yet you’re in for a treat. I found these videos on youtube yesterday of the Gemini demo from the BI conference last year that you can view below.

Gemini is a new part of the MS BI stack that is an add-in for Excel that allows power-users the ability to essentially create their own cubes using virtually any data they can get their hands on.

Being the MS BI geek that I am, this opens up all sorts of new opportunities for prototyping solutions and enabling the business to build their own BI applications.

The key here, that I see, is that these solutions are not managed by IT. So, as soon as one of these Gemini cubes becomes business critical, it will need to be built using formal BI methods and tools so that the proper support procedures can be implemented. This is what scares me :-S

I can foresee smaller businesses that are resistant to change, or are scared of the term “Data Warehouse” from prior failed projects, that would want to implement Gemini solutions as business critical applications. Simply because it’s cheaper to implement in the short term, ignoring the lack of sustainability that a more traditional BI solution yeilds.

Enough rambling for now, watch the videos and let me know what you think…

Sep 02

Recently I was having some issues getting a new SQL Server Analysis Services (SSAS) cube to process on a new development (dev) server. The error I kept receiving was:

[Analysis Services Execute DDL Task] Error: OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.; 08001; SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. ; 08001.

After much toying around I was able to determine what was causing this. In my case I had my shared data source connection for my data warehouse using Windows Authentication and the Impersonation Info set to Default. The problem appears to stem from the translation from Windows Authentication to the Impersonation Info option.

To fix this I changed my shared data source connection to use a SQL Server account and left the Impersonation Info option as default. This then must have allowed SSAS to translate the username and password info when doing the impersonation. I could be wrong but it is now working.

If you have any comments on this or a deeper explination please share? If you too are experiencing this issue o I hope this helps!