Work at Office, take it home - take what?

[dean12]

Brand new to Analysis Services. I'm spending tons of time coming up to speed ---- so....

I want to take the work home and continue from there.

At the office, I have a server running Analysis services and SQL Server 2000. I'm on a workstation.

At home, I have one machine to serve as the server and the workstation.

Does anyone do this - take stuff to work somewhere eles? What do I need to take?

Also, I had converted my Analysis Services to use a SQL database versus whatever it was using. So now I have a database called "AnalysisServices". I look in there and there are two tables, one of which has A LOT of information in it (OLAPOBJECTS). I looked at the "ObjectName" field that there appears to be lots of connection information. I'm nervous that when I transport this to another machine, that connection information may no longer work. How to resolve this? Or is it not a problem?

 

[MDXer]

Lets tackel the second part first. The SQL DB you have called AnalysisServices is the Repository. This is where Analysis services stores all of the information that defines what a cube is comprised of. Analysis Services ships with an Access repository but upgrading to SQL is highly recommended except is rare instances. Depending how large you cube structures are the Access Database can get quite large and also become corrupt.

As for the First Question as to what you need to work at home. That depends on what you need to do. If you developing the underlying tables that the cube is built from you could manage with just SQL running. If your Developing actual cube structures then you will need MS SQL (or whatever the DW runs in), MS Analysis Services, and a sampleing of the Data.

Currently (as a consultant) and in the past (as the company of an employee) I have always done a major portion of the development locally on my machine and the pushed it to an actual server to tune and tweak it. MSDN makes it affordable for a developer or a company to provide developers with local installs of the applications they need.

If a local install and data sample is not doable then you may see if they can provide VPN access to the network and Terminal Service access, but if your doing this on an analog line then you might want to reconsider the whole working at home idea (which I have opinions on but that is for another thread)



"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck

 

[dean12]

Thanks.

I've got a complete setup both here in the office and at home - SQL 2000 Server, Analysis Services, and Crystal Analysis 9.

So I took a copy of my database (complete with data) and installed that at home. I also took a copy of the database I designated as the repository home and installed that. Course when I migrated the repository on my home install of Analysis Services, it over-wrote that AnalysisServices database to I re-installed it.

Ok.

Honestly, the problem was that Crystal Analysis 9 will not "connect" to the OLAP server. I was able to connect to my database and do some cube development. Once I went to Crystal however, I couldn't connect to the cube. I can at the office but not at home.

So poking around today in the AnalysisServices database brought me to the OlapObjects and made me wonder if there might be something in there that differs between my office and home locations. Certainly the SQL Server name is different.

 

[MDXer]

I would look more at permissions on the server and make sure that all users are there and have the proper access rights. Also copying the Cube and repository database are not generally good ideas when moving to a diffrent server. If you need to move a cube you are much better off archiving on one server and restoring on another server.

"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck