Tell Me About Your DW Development Life Cycle
From: Deb Wolfe (thedebwolfe_at_hotmail.com)
Date: 05/05/04
- Previous message: dpuri: "Re: How to publish dashboard for SQL Server"
- Next in thread: Alejandro Leguizamo \(MVP\): "Re: Tell Me About Your DW Development Life Cycle"
- Reply: Alejandro Leguizamo \(MVP\): "Re: Tell Me About Your DW Development Life Cycle"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 4 May 2004 19:13:13 -0700
What are some good ways to get development cubes into
production?
I currently use a developer's edition of SQL Server 2000
with Analysis Services. In the past couple of years I
have been responsible for running reports. The plan now
is to let users run reports for themselves by connecting
to the Enterprise version at the client site via some
simple client tool.
The database is relatively small--just over 1 gig. There
are about 250K members (students) and 2 million facts
(test scores). I am responsible for doing ETL and
building cubes.
What sounds good?
1) Build everything locally and then just copy the .mdf
and .cab files to the Enterprise server.
2) Connect to the production server via VPN and run the
ETL statements against that database. Connect to the
Analysis Services Server and rebuild cubes. (Currently I
get an error message when trying to connect to the remote
server via Analysis Services although I can see it in
Enterprise Manager).
3) And the other logical possiblity--local database
(which is then copied to production) but remote analysis
services cube building.
- Previous message: dpuri: "Re: How to publish dashboard for SQL Server"
- Next in thread: Alejandro Leguizamo \(MVP\): "Re: Tell Me About Your DW Development Life Cycle"
- Reply: Alejandro Leguizamo \(MVP\): "Re: Tell Me About Your DW Development Life Cycle"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|