I have read a few articles about moving data out of SAP BW and into SQL Server. I cant find any articles on moving the data from SQL Server to SAP BW, is it even possible and if so what would be the best way to handle this?
After searching on this topic, i found many link addressing this issue, in this answer i will try to summarize them all and to provide all links that can help you achieving your goal.
There are many way to import data from SQL Server into SAP BW:
(1) SAP BW DB Connect
With DB Connect, you can load data from a database system that is supported by SAP, by
linking a database to the BW as a source system, thereby creating a direct point of access to external relational database management systems (RDBMS).
Making metadata known to BW by generating a DataSource.
Transferring Data Using DB Connect
Create DataSource for DB Connect step by step
SAP BW 7.3: How to extract data from SQL Server using DB Connect
Note 512739 - BW external DB Connect for MS SQLServer
(2) SAP BO Services
Creating a Data Store by using SQL Server Database
(3) SSIS - Microsoft Connector for SAP BW
Microsoft has created a SSIS connector for SAP BW, which allows you to create connection To SAP BW, you can refer to the following links and official documentations:
How to load data into SAP BW 7.3 from SQL Server using SSIS
SQL Server 2016
The Microsoft Connector for SAP BW consists of a set of three components that let you extract data from, or load data into, an SAP Netweaver BW version 7 system.
The Microsoft Connector for SAP BW for SQL Server 2016 is a component of the SQL Server 2016 Feature Pack.
Microsoft Connector for SAP BW
Microsoft Connector for SAP BW Components
SQL Server 2014
The Microsoft Connector 1.1 for SAP BW consists of a set of three components that let you extract data from, or load data into, an SAP Netweaver BW version 7 system.
Microsoft Connector 1.1 for SAP BW
SQL Server 2008
Using SQL Server 2008 Integration Services with SAP BI 7.0
If you decide to go with SSIS, I found this white paper from SAP that contains a detailed tutorials:
How to use Microsoft Connector 1.0 in
MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL
If this article didn't help, you can refer to tens of tutorials on how to create SSIS packages on the internet:
Steps to Create your First SSIS Package
SSIS Basics: Setting Up Your Initial Package
Create a new SSIS package/
Official integration services tutorials
(4) SSIS - Xtract IS BW Loader
This is a third-party tool created to allow SSIS to connect with SAP BW.
The Xtract IS Component Suite offers nine components to provide all kinds of SAP interface technologies. Implement your data flows in a secure and type-safe way with a graphical editor.
Xtract IS – Plug’n’Play for SAP and SQL Server Integration Services
Discussion
While searching for this issue, using SSIS to achieve that is not recommended because it may encounter some incompatibility issue, they recommended to use SAP BW standard anyDB source system or SAP BO Data services.
Issues example:
Loading Data from SSIS to SAP BW
Using SSIS to load data from SQL Server to SAP BW
SAP BW to SQl Server import and export wizard
On the other hand, SSIS guarantee the ease of use and there is thousands of topics and references for this technologies which will help you to achieve your goal faster than other technologies.
References and external links
How to load data from SQL Server to SAP BW using SSIS
Quick Tip: SSIS and SAP BW
-Setting up connection between SAP BW and SSIS
White paper - SAP BW transferring data with DB Connect
I guess the easiest way would be to use an ETL tool to extract data from MSSQL and insert into BW; specifically Microsoft's Integration Services (SSIS), which you likely already have with your SQL Server license.
SSIS is a visual tool specifically designed for ETL scenarios like what you described, and is easy to get started with, I'm guessing that this tutorial covers 90% of what you'll need to do.
However, you should also investigate if your license allows you to use the SSIS connector for SAP BW and test if it is a viable option to simplify writing to BW, as writing directly to BW's tables may not be an option (e.g. because of licensing restrictions and/or technical impact due to directly manipulating a closed system's database).
create the universe/ presentation layer using existing SQL Server DB. if there is no major transformation required ETL can be avoided
Related
I'd be happy if someone could help me.
I need to get data from PL sql developer oracle and import of sql server, I want to do automatic synchronization.
now I am exporting an Excel file from PL sql developer oracle, and load the file into sql server
The tool specifically built for this is Sql Server Integration Services (SSIS). You can create a data flow with source component using Oracle Driver and destination using Sql Server. You can even add transforms between the two to handle formatting and other tasks.
Here is a link to a series of videos on the topic. There is plenty of non - video materials as well if you prefer.
https://www.youtube.com/watch?v=LgB7zdyH0uI
I am trying to get the Microsoft Connector for SAP BW ver 1.1 working in our environment.
This is to push data into BW only not extract it.
I have put the LibRFC.dll in place on the SQL server and can create a connection to BW. When I test the connection in SSIS it says OK so I know this bit is fine.
When I do a test load I get an RFC failure.
I have setup my Info cube and any necessary objects in BW.
I have even looked on the gateway and can see the attempts but I need to interrogate the error at a lower level to find out what is going on.
I am using SQL 2008 R2 with the Sap BW connecter version 1.1.
Can anybody offer me any help with this issue as its becoming quite critical.
We want to pull data from Redshift database into SQL Server. Currently, we are using SQL Workbench to analyze Redshift database. We referred the following link -
Connect Your Cluster By using SQL Workbench
Here we used - RedshiftJDBC41-1.1.17.1017 driver to connect.
Now we want to push this data to DWH in SQL Server 2016.
So what is the best way to accomplish this? There is not much information on net on how to pull data from Redshift.
Can we have SSIS component or something in SSDT/SSIS2015 to load this data?
Or can we have a middle layer of any tool (any ETL tools or Excel) which will dump this Redshift data into CSV or something which will be readable in SSIS?
Data from Amazon Redshift can be extracted and consequently loaded into almost any platform.
You have several options to move data from Redshift to SQL Server.
ETL Tool - You can use a commercial ETL tool. SSIS is a
perfectly legitimate way to extract from Redshift and to land the
data in SQL Server.
S3 Files - You can unload the data from Redshift into S3 buckets and
then use SSIS or bcp to copy data from buckets to your SQL Server
Local file system -- You can run the unload command to extract data
to local file system. You can have psql running locally in a server
inside of your network.
For information on how to connect SSIS and any other ETL or BI tool to Redshift please see this link.
Amazon Redshift provides ODBC Connectors which is not supported by any Sql Server BI Tools. MS BI stack only support OLE DB Providers and it is being provided by a third party vendor
I am trying to build SSAS cube sourcing data from Amazon RedShift.
Intern at a company. Learning SSIS. When I am connecting a data source to CRM 4.0. Am I to create connections for both OLE DB and ODBC or just ODBC?
Take a look at: http://blogs.msdn.com/b/crm/archive/2008/05/07/integrating-crm-using-sql-integration-services-ssis.aspx
To be able to make updates and create records you really need to use a web service as described in the blog above.
OLE DB Drivers would help you connect to the SQL Database that CRM 4.0 is using, but that would be no different than just connecting to a MS SQL Database. If you want to transfer data, manipulating the database directly is unsupported (and a bad idea).
Which software can you recommend to sync data from a FoxPro source to a SQL Server destination?
Here are a couple links with information that might be of help:
Migrating From Visual FoxPro
VFP conversion to support SQL server Backend
At my company we have data being written to foxpro tables daily, and are synced to SQL Server nightly using SSIS, so for the actual conversion I recommend that.
Getting the foxpro data to your central location could be accomplished by transferring the foxpro files via FTP (we've done this for years), or you could set up some sort of Web Service.
I don't think you'll find a tool to do this automatically and on a scheduled basis especially if they are geographically remote and the sync has to happen over the public internet. I'd be looking at writing a web service of some sort, which will sit on a server on the VFP side with methods to expose the VFP data, and another service on the SQL Server side to access that web service periodically and perform CRUD operations.