Sap r/3 to sql 2000/2005

Hi All,
We are trying to pull transation data from SAP R/3 to sql 2000 server. Should I build DTS by connecting to backend of sap R3 or do I have any way I can load data directly from SAP R3 independent of data base connected to R3.
Regards,
Kranthi

Hi Kranthi,
If you are trying to get the SAP R/3 master and transactional data into SQL server then you have many alternatives:
1. There is Visual Studio that you can use to get the SAP data in. Just follow the steps given at http://msdn2.microsoft.com/en-us/library/cc185254.aspx
2. You can use Xtract IS tools. They allow you to get data from any SAP table, infocube, SAP query, BAPI, hierarchy or a report. You can get more information at http://www.theobald-software.com/cms/en/xtract-is/xtract-is-bw-cube.html
4. Some BI connectors will be delivered in the SQL feature pack if you want to go that route. For more information, go to http://s3.amazonaws.com/jef.mindtouch.com/1007230/32/0?AWSAccessKeyId=1TDEJCXAPFCDHW56MSG2&Signature=r/U/Af2NFhN89GInha2%2bR2Tiuo4%3d&Expires=1209070349
Regards
Pravin

Similar Messages

  • Data extraction from SAP r/3 to sql 2000, bpc server

    Hi All,
    I have posted a similar thread previously,sap r/3 to sql 2000/2005, and understood how to transfer data from SAP R/3 to SQL 2005, but I need to transfer data from SAP R/3 to SQL 2000 server, not SQL 2005 server.
    Any help will be greatly appreciated.
    Regards,
    Kranthi.

    If you want to extract SAP R/3 data to SQL 2000, here are some alternatives:
    1. It becomes very easy if by any chance, you are using SAP BW with SAP R/3. You can extract the data into BW using standard or custom extractors and then send it out with open hub. SQL2000 can pick the flat files from a specified location at regular intervals.
    2. You can use Business Object extractors. You can get more info at:
    http://www.france.businessobjects.com/pdf/products/dataintegration/rapid_marts_sap_infosheet.pdf
    3. If that is not an option, then you need to have a tool that allows being called via RFC. This agent will then execute the required command on behalf of your application and return the result. I do not know if there is a ready-to-use RFC-compliant agent for SQL Server. If you have a tool that does it for you, you might have to check your network connections (ping), permissions etc. and see if you can execute an rSQL from the remote machine on the SQL server.
    There is a general solution to connect to nearly any kind of modern server application from a remote site by using simple HTTP requests. Suitable HTTP server for most needs would be:
    1. Microsoft IIS
    2. Java Tomcat or IBM WebSphere
    3. SAP WebAS
    In most cases, the IIS would probably be the one as it is installed on the Windows 2000 server anyway.
    Define an Active Server Page (ASP.NET) and insert the necessary code in your favorite language to extract the data from the SQL server.
    Your ASP.NET page would pack the result in the HTTP response object to be returned. In order to call the page from SAP you call the function modules HTTP_POST (using a HTTP POST request) or HTTP_GET (for HTTP GET request) on the standard RFC destination SAPHTTPA. (Pointing to a SAP utility program saphttp that resides in the SAP binary directory of your SAP database server and can be called from the command line in order to test its functionality without RFC).
    Regards
    Pravin

  • SAP 2007 A and SQL 2000

    I understand that SAP no longer supports SQL Server 2000, but could someone confirm whether I can still still install and run SAP 2007 with a SQL Sevrer 2000 database?

    Hi John,
    please have a look at the 'Product availability' landing page (Channel Partner Portal -> Solutions -> SAP Business One -> Product Availability):
    Apr 17 | Microsoft Has Retired its Mainstream Support for SQL 2000 as of April 8, 2008.
    For SAP Business One users still running their installation on SQL 2000, this means no new functionality or Service Packs. Microsoft will continue to provide bug fixes and security fixes on demand only. We therefore recommend that customers upgrade their SQL installation to 2005 as soon as possible. Refer to SAP Note 928839 for additional information.
    You will also see in the 'server' section that SQL 2000 is not supported for SAP Business One 2007.
    All the best,
    Kerstin

  • SQL 2000 - 2005 Upgrade - Windows IA64

    Hello
    We are shortly to upgrade our test systems to SQL 2005 for Itanium systems.
    We propose to use method number II in Note 799058 - "II  UPGRADE FROM MS SQL SERVER 2000 to MS SQL SERVER 2005"
    The SAP components are all WAS 7.0 with Support Pack Stack 07.
    Does anyone in the community have information regarding the run time of the upgrade and/or any problems?
    Thanks

    Hello Maria,
    In reply to your post and your email:
    The process to perform the migration you describe is relatively easy. While note 799058 is relevant, you should first have a look at the System Copy Guide, which applies to your system. These guides can be found on SAP Service Marketplace:
    “Release & Upgrade Info”  “Installation & Upgrade Guides”  “SAP NetWeaver”  “SAP NetWeaver 7.0 (2004s)”
    Click on “Installation”, a new window opens. Check section “Installation - SAP NetWeaver Systems”
    You will see links to system copy guides for Service Release1 and Service Release 2, and separate entries for ABAP only systems, Java only systems and double stacks.
    For example: the SR2 guide for ABAPJava has the title: System Copy for SAP - Systems Based on SAP - NetWeaver 7.0 SR2 - ABAPJava”
    Each of this guides has a brief chapter on copying a MSSQL database. Please carefully read the guide and the SAP notes it refers to. The overall procedure for an ABAP only system will look like this:
    1. Apply note 600027 (change SQL Server collation) to your existing SQL2000 database. You HAVE to perform this step before moving the database to the new hardware.
    2. Prepare your new servers (Windows, SQL2005 installation following the SAP guidance on collation et cetera).
    3. Detach the SQL2000 database from your old system, copy the datafiles to the new machine and attach the database to the new SQL2005 server.
    4. Follow the system copy guide and run sapinst to install the SAP central instance and configure the database.
    Copying the Java stack is a little bit complicated, because you have to create an export of your Java data on your old system first. This is explained in great detail in the system copy guide.
    Best regards,
    Christian

  • Installing SAP R/3 with SQL Server 2005..

    Hi,
    Microsoft is about to release "SQL 2005" in Nov05. Has anybody in here thought of installing/upgrading SAP on MS-SQL's latest version of the database server. On doing some research on the net I noticed that Microsoft has already upgraded their SAP R/3 environment to the beta edition of SQL Server 2005. I did not find any information on SAP having certified SQL Server 2005 yet.
    Do we have to wait till ECC6.0 or whatever the new version of ECC would be to leverage the SQL Server 2005 D/b ?
    Any thoughts/information on the readiness of SQL Server 2005 for SAP R/3 would be appreciated.
    Jay

    Hi Jay,
       Past experience says SAP won't support a new platform (e.g. DB, OS, etc) until they have had a chance to test it.  Your official SAP document for what is supported is in the Product Availability Matrix.  http://service.sap.com/pam
    With that said, that doesn't mean that you can't try it out. Of course not in a test environment. You get some very good learning experiences from trying.  But don't enter a customer message about a non supported platform.
    Good luck,
    John

  • B1 and SQL Server 2005 performance with 3.000.000 invoice-lines per year

    I would like to know if SAP Business One with SQL Server 2005 could work with the following information:
    - 40.000 Business Partners
    - 40.000 Invoices per month
    - Aprox. 3.000.000 invoice-lines per year
    Of course it will be necessary to change some forms in B1.
    What do you think?
    Do you know any B1 customer working with that amout of data?

    > Hi,
    >
    > I think a good SQL2005 tuning (done by a good DBA)
    > will improve performance. Number of records like that
    > shouldn't hurt that kind of DB engine...
    Hi,
    I'm sure that MSSQL2005 can handle the amount of records & transactions in question. Even MSSQL 2000 can do it. However, any DB engine can be put on its knees with the combination of 2-tier application architecture and badly designed queries. B1 is a case in point. I wouldn't go into such a project without decent preliminary load testing and explicit commitment for support from SAP B1 dev team.
    I have heard from implementation projects where B1 simply couldn't handle the amount of data. I've also participated in some presales cases for B1 where we decided not to take a project because we saw that B1 couldn't handle the amount of data (while the other features of B1 would have been more than enough for the customer). The one you're currently looking at seems like one of those.
    Henry

  • Downgrade to sql 2000

    Hi,
    We are doing a system migration from one hardware platform to another. We do this by installing a new SAP server + SQL server on the new hardware, detaching the data from the source system, attaching on the target system and running STM.
    Source system setup is: Win2003, SQL2000, SAP ECC 6.0
    Target system setup is: Win2003, SQL2005, SAP ECC 6.0 <-- SQL server 2005 was erroneously chosen by us
    Now, the question is: How can we downgrade the target system to SQL 2000? Do we have to re-install the system all over, or is it sufficient to delete SQL 2005 and install SQL 2000?
    Has anyone tried this?
    Go-live is Friday, so we are in a hurry
    Thanks
    Thomas

    Hi,
    Thanks for your interest.
    Yes. First of all SQL 2005 is 'wrong' because the source system is on collation "bin" whereas the target system must be on collation "bin2" if it is an SQL server 2005. The source systems cannot have "bin2" installed because it will require downtime in the source system and we can't have that.
    We have done a test where we run the target system SQL 2005 with collation "bin" and then attach the database. That works fine, apart from loads of messages coming out of transaction SICK:
    DB CHECK   Wrong Database collation. Perform SQL2005 after upgrade steps. Please see note 126973
    DB CHECK   DB CHECK   DB CHECK   DB CHECK   DB CHECK   DB CHECK   DB CHECK   DB CHECK   DB CHECK   DB CHECK
    Severe problems were detected during initial system check.
    Please, do not use that system before fixing these problems.
    I have checked the mentioned note, and also notes 600027, 62988, 126973, 799058, 924288 and 1291861. None of them seem to fix the problem. So we decided to forget about the SQL server 2005 for the weekend and instead go for a 1:1 correlation between source and target systems, and then plan for a SQL 2005 upgrade later.
    What are your thoughts? Can SICK be fixed?

  • MS SQL Server 2005 Developer Edition

    Hi,
    We are developing a legal management product on SAP platform
    We would have  SQL Server to be used as a database for SAP ECC 6.0 in DEVELOPEMENT environment
    The landscape of the planned development  environment  has a total of 8 servers. We understand that a separate MS SQL Server 2005 ( Question :- Enterprise / standard / Developer ??? ) edition is required for all the servers Each server will run its own instance. Each server will have 2 Intel Xeon CPUs with quad cores.
    We understand that there will not be any users accessing the database directly. Instead, the SAP ECC software will create its own schema and users ( at most 4).
    1) Please let us know which edition is best suitable for us for above scenario .
    2) Does SAP ECC work on SQL Server 2005 Developer edition ?
    3) Can we have  one instance of SQL Server be used and multiple databases for dev, qa and prod be created from it
    Your prompt response will much be appreciated
    Thanks a ton !

    1) Please let us know which edition is best suitable for us for above scenario .
    SAP ONLY supports Enterprise edition.
    2) Does SAP ECC work on SQL Server 2005 Developer edition?
    No SAP willnot work on SQL Server 2005 edition.
    3) Can we have one instance of SQL Server be used and multiple databases for dev, qa and prod be created from it.
    Yes, technically it is possoble. But not at all recommended by SAP.
    Regards,
    SK

  • List of logins sql 2000 - 2008

    can anyone let me know which table in sql 2000, 2005 and 2008 lists all server level logins in a sql instance? Is it the same view/table per version (i.e. 2000--2008)?

    can anyone let me know which table in sql 2000, 2005 and 2008 lists all server level logins in a sql instance? Is it the same view/table per version (i.e. 2000--2008)?
    Hi,
    Syslogins conatain one row for each login account
    http://technet.microsoft.com/en-us/library/ms178593.aspx
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • How to install mini SAP in MS SQL Server 2005 Express?

    Hi, is anyone know how to install the mini SAP v4.6 by using MS SQL Server 2005 Express?
    I get error when connecting to the Database at 88% of the installation.
    Please help. Thank you.

    I do not think you can install miniSAP 4.6D on MS SQL server 2005 express.
    1) you need the up todate patch to run on MSSE. If  SAP did the work to allow it to run, it would be patch 55+. As supplied it is patch zero.
    2) You can install on MSDE (MS SQL server 2000) patch 4. Look for my post INFO: Installing MiniSAP 4.6D on a named instance of MSDE (MS-SQL).
    3) after the install on MSDE SP4 you would have to change the database code page to 'BIN2' look for the OSS note.
    4) then you can start patching through to the most recent.
    The main reason you cannot do this is MS have changed the version key format to include '.6' as extra info which SAP cannot interprate, too many dots.
    MattG.
    Message was edited: add URL

  • Upgrade R/3 4.7 110 from SQL 2000 to ECC 6.0 /SQL 2005

    Dear Experts,
    We are currently running R/3 4.7 110 with kernel 640 32 Bit Non Unicode on Windows Server 2000/ MS SQL 2000 Platform. We are planning to Upgrade the same to ECC 6.0 on Windows 2003/ SQL 2005 on New x64 Bit Hardware.
    I was earlier planning to Upgrade the OS/DB in first Phase moving the same R/3 4.7 on Windows 2003 Server /MS SQL 2005 and then Upgrade it to ECC 6.0 in second phase. But to my surprise when I checked PAM, I found that R/3 4.7 110 is not at all supported on SQL 2005 ( though R/3 4.6 C is)
    Now shall I upgrade it to ECC6.0 First with Windows 2003/SQL 2000 ( Because ECC6.0 is supported with MS SQL 2000)and then move to MS SQL 2005 ?
    Thanks
    Jitendra Tayal

    We had the same issue.
    So I checked with SAP.
    This was their reply.
    'SAP R/3 4.7 Ext 110 is supported on SQL 2005. Please refer to the following notes for further information:'
    Note 905634 - Release planning for Microsoft SQL Server 2005
    Note 799058 - Setting Up Microsoft SQL Server 2005
    Note 899111 - Installing R3 4.7SR1 (47X110) on x64 Windows Platform
    Note 151603 - Copying an SQL Server database
    So feel free to go ahead.
    Thanks.
    Carl.

  • Database restore from SQL 2000 to SQL 2005 for SBO 2005B

    Hi Everyone,
    I am facing some problems in regards to the restore of SBO Database from SQL 2000 to SQL 2005.
    Let me explain you the problem.
    See I am using SAP B1 2005B with patch level 38 in my laptop with SQL 2000. I have made an company in this and done work in it as a production company and now I want to restore this company in the server which has SQL 2005. How to do it.
    I have taken a backup in my laptop from SAP B1 Server Suite Manager which has SQL 2000 and sucessfully backed up but when I am trying to restore in the server which has SQL 2005 I am getting the following error in SQL 2005 in server :-
    Restore failed for Server 'DXBAP001'.  (Microsoft.SqlServer.Smo)
    System.Data.SqlClient.SqlError: Directory lookup for the file "C:\Program Files\Microsoft SQL Server\MSSQL\data\SBO_DCHAR.mdf" failed with the operating system error 3(The system cannot find the path specified.). (Microsoft.SqlServer.Smo)
    Please let me know the solution for it.
    Thanks in Advance.
    Regards,
    Kawish Junaid Mazhari

    Hi,
    In SQL 2005 create a database and name as the 200 one was (though any name would do).  when you create the database note the location of the .mdb and .ldf file.
    once this had created right click on your new database > tasks > restore database
    in the new window select from device and point it to your .bak file created from your 2000 system, ensure you put a tick in the restore box on the new line.
    in the options tab tick overwrite database, and, change the file locations in the restore as directory to the file locations of the new database.  the file names must be the same too.
    you can change the original file names after the restore.
    that should do the trick.
    thanks,
    mike

  • HOM: MS SQL Server 2000 - MS SQL Server 2005 [sp sap_use_var_MAX]

    Hi guys,
    Procedure
    Homogeneous System Copy on SQL Server
    Source Platform
    Windows 2003 Server x86
    SQL Server 2000 SP4
    SQL_Latin1_General_CP850_BIN2
    SAP R/3 4.7 x200
    SAP Kernel 6.40 Patch 347 x86 (Sep 10 2010)
    SAP_BASIS 620 Patch 69
    Target Platform
    Windows 2008 Server x64
    SQL Server 2005 SP3
    SQL_Latin1_General_CP850_BIN2
    SAP R/3 4.7 x200
    SAP Kernel 6.40 Patch 347 x64 (Sep 10 2010)
    SAP_BASIS 620 Patch 69
    Symptom
    When running STM (SAP Tools for SQL Server) on the target server I get the following error:
    - Errors when executing sql command: (Microsoft)(ODBC SQL Server Driver)(SQL Server)Could not find stored procedure u2018sap_use_var_MAXu2019.
    Further Analysis
    I'm able to start the SAP system.
    Tx SICK returns the following:
    - Wrong long datatypes. Perform SQL Server after upgrade steps. Please see note 126973
    Troubleshooting
    Note 126973 - SICK messages with MS SQL Server
    Solution:
    Proceed as described in Note 1291861
    Note 1291861 - SICK message: Wrong long datatypes
    2. If the problem occurred following a system copy from SQL Server 2000 to SQL Server 2005 or later then execute the following statements:
      setuser 'sid'
      exec sap_use_var_MAX
    Where 'sid' is the SAPSID of your system in lower case.
      setuser 'dev'
      exec sap_use_var_MAX
    Msg 2812, Level 16, State 62, Line 2
    Could not find stored procedure 'sap_use_var_MAX'.
    Request
    I'm thinking if any one of you is able to access an SAP system on SQL Server (2005 or other) with the above mentioned stored procedure present you could scipt it to a txt file and post it here in order for me to create it manually on my system.
    I've checked several SAP Notes on this subject and none of them explains how to create this store procedure from scratch, they all just assume it's already there and tell you to execute it.
    Thank you.
    Bruno Pereira

    I was able to solve this issue just now the following way:
    - A friend of mine scripted it to a file which I then used to create the sap_use_var_MAX on the target database.
    Here is a copy of that file:
    USE [<SID>]
    GO
    SET ANSI_NULLS ON
    GO
    SET QUOTED_IDENTIFIER ON
    GO
    create proc [<sid>].[sap_use_var_MAX] as
    begin
      declare @tabname sysname
      declare @colname sysname
      declare @datatype sysname
      declare @nullflag nvarchar(1)
      declare @cmd nvarchar(1024)
      declare @n_altered int
      declare c cursor for
        select t.TABLE_NAME,c.COLUMN_NAME,c.DATA_TYPE,
                  nullflag = substring(c.IS_NULLABLE,1,1)
          from INFORMATION_SCHEMA.COLUMNS c,
               INFORMATION_SCHEMA.TABLES t
          where c.TABLE_NAME = t.TABLE_NAME AND
                c.TABLE_SCHEMA = t.TABLE_SCHEMA AND
                t.TABLE_TYPE like '%TABLE%' AND
                c.TABLE_SCHEMA = schema_name() AND
                c.DATA_TYPE IN ('text','ntext','image')
          order by t.TABLE_NAME,c.COLUMN_NAME
      open c
      set @n_altered = 0
      fetch next from c into @tabname,@colname,@datatype,@nullflag
      while (@@fetch_status <> -1)
      begin
        if (@@fetch_status <> -2)
        begin
          set @cmd = N'alter table [' + @tabname +
                      N'] alter column [' + @colname +
                      N'] '
          if @datatype = N'text'
            set @cmd = @cmd + N'varchar(MAX)'
          else if @datatype = N'ntext'
            set @cmd = @cmd + N'nvarchar(MAX)'
          else
            set @cmd = @cmd + N'varbinary(MAX)'
          if @nullflag = N'N'
              set @cmd = @cmd + ' NOT NULL'
          else
              set @cmd = @cmd + ' NULL'
          -- print @cmd
          exec( @cmd )
          set @n_altered = @n_altered + 1
        end
        fetch next from c into @tabname,@colname,@datatype,@nullflag
      end
      close c
      deallocate c
      select convert(varchar,@n_altered) + N' columns were altered'
    end -- sap_use_var_MAX
    Mind you, you'll have to change <SID> and <sid> acoordingly, considering also if your db is dbo schema or sid schema owned!
    Thank you for your help nonetheless!
    Bruno Pereira

  • SQL 2000 AND SQL 2005 ON THE SAME SERVER

    Hi all ,
    I have an installation of    SAP4.7SR1 /MSSQL2000 on a windows 2003 server.
    I want to install SAP SOLUTION MANAGER 4.0 /MSSQL2005 on the same server ... it is possible that two version of SQL ( 2000 and 2005 ) coexists on the same server ? It's sufficent to install SQL into two different directory ?
    Thank's a lot.
    Antonio Voce.

    Hi,
    yes it is possible to install SQL2000 and SQL2005 on same server but there are certain special considerations that you should be aware of
    look at following blog
    http://blogs.msdn.com/sqlblog/archive/2006/09/27/co-existence-of-sql-2005-with-sql-2000.aspx
    also look http://msdn2.microsoft.com/en-us/library/ms143694.aspx
    but in case of SAP Installation i prefered that to upgarde SQL2000 to SQL2005  then install solman 4.0
    regards,
    kaushal

  • Upgrade SQL Server 2000to SQL Server 2005 in an SAP environment

    Hi,
    I have a scenario in which we are going to upgrade SQL server 2000 to SQL server 2005 in SAP an environment.
    Now SQL server has a concept of In-Place Upgrade and Side-by-Side Migration Process.I want to know what does both of these mean.
    We have an SAP note(799058.It talks about the upgrade in Step II.Is it the same as In-Place Upgrade concept in SQL?
    What is step III in the note talking about? Is it talking about Side-by-Side Migration?
    It would be of gr8 help if someone could provide the conceptual knowledge on these and what does the note mentioned above talks.

    Hello
    Please review my post on SQL upgrade.
    SAP on SQL Server
    You may also like to review
    http://www.microsoft.ie/downloads/itprosql-90.ppt#568,17,Demo
    Can you please advise your DB size and the max. amount of downtime your business can afford?
    I will check, but I am almost sure that a side-by-side SQL upgrade is not appropriate for SAP systems.
    Thanks
    N.P.C

Maybe you are looking for