Hi,

we're about to try writeback forecast data to our AS cube
from Excel. Many questions arises:

1. Is writeback included in SQL server Standard edition ?
2. We use oracle 8.1.7, is writeback possible ? Any
differences to be aware of from writeback to SQL Server ?
3. We have in our cube many dimensions including virtual
dimension. We also have many measures. Is it a good design
principle to use a separate cube for writeback with only
the forecast-related dimensions and measures ?
4. Any good code samples ?

/jerome

1) No
3) Yes (this lets the dims have different grain as well)

Re "We also have many measures" ... Not optimal. Does your cube have an
Account dimension?

tom @ the domain below
www.tomchester.net


"jerome" <jrmkjrm (AT) hotmail (DOT) com> wrote

Jerome

Writeback and other advanced features are available through the SQL Server
Enterprise and Developer editions. If you want more information I can email
you some information that will explain the differences between the different
versions.

There are also numerous ways to budget, forecast and collect data under AS.
Features such as equal allocations, equal increments, weighted allocations
and weighted increments may be of interest to you. You may want to see the
different options that are available and how to optimise the performance for
AS with writeback.

There are also different ways to achieve writeback for AS as well. How are
you currently achieving writeback to AS?

Regards
Howard Taylor CA(SA)
Business Intelligence Manager
O2OLAP Limited

tel: +44 (0)20 8785 4811
fax: +44 (0)20 8789 1589
mobile: +44 (0)7831 332234

email: Howard.Taylor (AT) o2olap (DOT) com
web: www.o2olap.com

"jerome" <jrmkjrm (AT) hotmail (DOT) com> wrote

Anyone who knows about how writeback works under the "hood"? What stored
procedures or SQL-batches are used. Is there any use of extended stored
procedures?

Regards
Thomas Ivarsson


"Howard Taylor [O2OLAP]" <Howard.Taylor (AT) o2olap (DOT) com> wrote

Jerome,

1. I agree with Nigel, the standard edition does allow writeback; I've
done it!
2. No problem using Oracle; you could even use Access if desired.
3. It's usually best to have a forecast cube because the actuals are
often on a much finer grain than the forecasts.
4. Don't reinvent the wheel; use a Excel add-in (XLCubed, BIXL, MIS
Plain, Visual OLAP & although I haven't seen the released version
Howard's O2OLAP).

Regards,

John


"jerome" <jrmkjrm (AT) hotmail (DOT) com> wrote