We are starting a BW 3.0A pilot. The Pilot will use mostly non-SAP data (from MS SQL) and a little R/3 data (4.6.C). Our current R/3 apps are on Unix/Informix with WIN appl servers. We would have a small to medium T-Shirt size BW Central Instance on WIN2000/MS SQL. The price is right, since we have a 4 CPU Dell server available with 4GB RAM and 150GB disk. If we have equal skills in both platform/DB areas, is it prudent jumping to WIN2000/MS SQL and not continuing with Unix/Informix for all SAP appls regardless of short-term cost? Will we run into later Extractor compatibility issues? Or WIN scalability limits? And are we creating set-up and administration issues?
I am not aware of comprehensive training or guide for release specific installation or migration
of BW3.0A/APO for SAP consultants, but it sounds like a good idea!
Some typical problems are in the installation guide and configuration issues to watch for small data amounts are documented in OSS. For introduction information see SAPNET BW and database optimizer.
In brief data problems exist with SQL because SAP stores data which is not always accessible and ABAP/4 supports a limited version of ANSI SQL, therefore limits capabilites contained in ANSI SQL tables and joins with non-SAP data. For more information on scalability see the guides to BW and you may contact my collegues at www.sap.hp.com/public (mySAP BI)
Please contact us for our SAP newsletter at www.sap.hp.com/public
This was first published in April 2002