SQL 2000 or SQL 2005

Dear All,
I want to know which SQL database you think is secure and safe for SAP Business One 2005B.
Should the client install SQL 2000 or SQl 2005. What is your exprience for it.
Regards

I would say more than Security, SQL Server 2005 is recommended for SBO2005. 
Please read documentation available on this Page.
https://websmp108.sap-ag.de/smb/sbo/documentation
Suda

Similar Messages

  • Can SQL 2000 and SQL 2005 drivers co-exist in PI?

    Hi,
    Currently in our PI environment, we have JDBC Adapter connections to SQL 2000 database servers for which the Driver has already been installed.
    For connecting to new SQL 2005 database servers, I understand that we have to install the SQL 2005 drivers. I also came to know that SQL 2005 Driver is backward compatible and supports JDBC connection to SQL 2000 server.
    But the question I have is whether both the SQL 2000 and SQL 2005 drivers can be installed together in a way that connection to SQL 2000 use the 2000 driver and the connection to 2005 uses 2005 Driver.
    (They have different connection strings)
    Many thanks in advance,
    Regards,
    Rosie Sasidharan

    The SQL Server 2005 JDBC driver is far better than the SQL Server 2000 JDBC driver.  The 2005 JDBC driver primarily consists for one file, sqljdbc.jar.  ( if you want to use windows authentication there is another file you would need based on your platform x64 vs x86 called sqljdbc_auth.dll. If in the connect string you list ;integratedSecurity=true which means integrated security would be used and this second file would be required.  The 2000 driver did not support integrated security.
    The SQL 2000 JDBC driver was made up of the 3 jar files:
    msbase.jar,mssqlserver.jar and msutil.jar.
    If you want to use a Microsoft JDBC driver to connect to SQL Server 2005, than you should use the 2005 driver, sqljdbc.jar.
    Follow the instructions in point 1 of the note #831162 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 JDBC Adapter questions 1 and 13.
    Since the jar are different I assume you can use the both drivers, but it doesnt make sense.

  • 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

  • Upgrade windows 2000 t o windows 2005 and sql 2000 to sql 2005

    Dear People,
    i have not actually done any upgradestill now, i have task where i need to upgrade existing sap system.The sap has already been upgraded, now my task is to upgrade operating system and database
    requirement:
    windows 2000 to windows 2003
    sql 2000 to sql 2005
    the above should be done by the procedure recommended by sap only, so im wondering where i can find the information and tools for uprading both O/S and DB.
    Help
    Raj

    I personally would not do a Windows upgrade, Windows can be very picky when it comes to 3rd party SCSI/FC drives you may experience bluescreens during the update after the second boot etc.
    I would backup the system and install the operating system from scratch and do a system copy instead.
    For your database upgrade, there's a guide at
    http://service.sap.com/instguides
    --> Other documentation
    --> Database upgrades
    Markus

  • Migrate SQL 2000 to SQL 2008

    Hi,
      My company needs to migrate SQL 2000 to SQL 2008.  The SQL 2000 server is running on Windows 2000 server and SQL 2008 does not support Windows 2000 server, so we can't upgrade it to SQL 2008.  Also, double upgrade (SQL 2000->SQL 2005->SQL 2008) is not an option, because we have a very very short time frame.
      The only option I can think of is manually copy everything from SQL 2000 to SQL 2008.  This is ok for tables, views, stored procedures, and functions, but how about triggers, DTS packages, and jobs?
      Is there a good tool out there can copy triggers, DTS packages, and jobs?  Or can somebody recommend another way to migrate SQL 2000 to SQL 2008?
    Thanks,
    Wei

    You can Save AS dts as a file and open on the new server . Read about DTS Designer tool to run the packages
    https://technet.microsoft.com/en-us/library/aa225178%28v=sql.80%29.aspx
    All jobs AFAIK you can script out and re-run on the destination server
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • 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 2000 to SQL 2005 --- schema conversion error

    Hi, I execute an upgrade from MSSQL 2000 to MSSQL 2005 and everything executed succesfully. Then i download the "SAP Tools for MSSQL Server"
    to execute the schema conversion of the database. But i get an error when a step tries to create the stored procedures in the db. Specifically i get the error in the sap_blocked_procccess store procedure with the following error:
    ERROR 2006-12-07 10:19:57
    FCO-00011  The step ExeProcs with step key |SAPMSSTOOLS|ind|ind|ind|ind|0|0|MssSysCopy|ind|ind|ind|ind|4|0|MssProcs|ind|ind|ind|ind|4|0|ExeProcs was executed with status ERROR .
    ERROR 2006-12-07 10:19:57
    MDB-05053  Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.
    INFO 2006-12-07 10:30:00
    An error occured and the user decided to retry the current step: "|SAPMSSTOOLS|ind|ind|ind|ind|0|0|MssSysCopy|ind|ind|ind|ind|4|0|MssProcs|ind|ind|ind|ind|4|0|ExeProcs".
    ERROR 2006-12-07 10:30:29
    FCO-00011  The step ExeProcs with step key |SAPMSSTOOLS|ind|ind|ind|ind|0|0|MssSysCopy|ind|ind|ind|ind|4|0|MssProcs|ind|ind|ind|ind|4|0|ExeProcs was executed with status ERROR .
    I didn't find any note or something else.
    Do you have any idea about this problem?
    Best Regards,
    Thanasis

    Hello,
    please ensure that the Database compatibility level for all databases is 90 by
    running
    exec sp_dbcmptlevel 'master',90
    exec sp_dbcmptlevel 'model',90
    exec sp_dbcmptlevel 'msdb',90
    exec sp_dbcmptlevel 'tempdb',90
    exec sp_dbcmptlevel 'EA5',90
    Then rerun the STM tools.
    Regards
      Clas

  • Migration of SQL 2003 to SQL 2012

    Hi,
    Can someone help me address issue in migrating SQL 2003 to SQL 2012?  What's the best practice in such migration?
    Do I need to upgrade it to 2005, 2008 first before migrating it to 2012?  Please advise criticality on this issue and best practice as well.  Thank you.

    Hi  arkimuza23,
    There is no SQL Server 2003, could you confirm the exact version? If your version is SQL Server 2000, we will be not able to migrate from SQL 2000 to 2012 directly. SQL Server 2012 supports upgrade from only the following versions: SQL 2005 SP4,SQL 2008
    SP2,SQL 2008 R2 SP1 or later .
    Migration from 2000 to 2012 requires an intermediate step. We will have to make the migration in two steps:
    - Step 1: Make a first migration from SQL 2000 to SQL 2008 for instance. You need to be SQL 2000 SP4, then follow this step : Migration SQL Server 2000 to SQL Server 2008
    - Step 2: Make a second migration from SQL Server 2008 to 2012.
    Supported Version and Edition Upgrades
    http://technet.microsoft.com/en-us/library/ms143393.aspx
    Migration SQL Server 2000 to SQL Server 2008
    http://blogs.technet.com/b/mdegre/archive/2009/07/21/migration-sql-server-2000-to-sql-server-2008.aspx
    Thanks,
    Candy Zhou

  • 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.

  • What is SQL 2000 mode in SQL 2005 Server?

    I have a application which will work in SQL 2000 (literally). I am upgrading my SQL server to 2005 from 2000. I want to know how to make SQL 2005 to function as SQL 2000 so that my application will continu working with 2005 too..?
    In other words where is the option as "Run this program in compatibility mode for" like we have in Windows?
    I appreciate all your help.
    Ping me in Yahoo IM : rajeshtheodore too

    Which Oracle product? You've only mentioned two Microsoft products and an unnamed application so far.
    In other words where is the option as "Run this program in compatibility mode for" like we have in Windows?Do you mean an option in this application that works on SQL Server, or an option in SQL Server 2005? Why would we know anything about either of those?
    ~Edited by: William Robertson on Sep 23, 2008 7:25 AM~

  • Changes required to switch from SQL Server 2000 to SQL Server 2005?

    I'm converting a legacy app from SQL Server 2000 to SQL Server 2005.  The app is written in VB6 and utilizes CR 8 OCX.  When I invoke a report from VB I'm getting Error# 20599 Cannot open SQL server.  I redefined the ODBC DSN specifying Windows Authentication, and the SQL Server instance supports mixed mode.
    Searching for the error, I found an article that suggests I need p2sodbc8.zip, but I can't find a link to it in the Downloads area.
    Would greatly appreciate any help at all - including a link to p2sodbc8.zip if that's the likely resolution.
    Thanks in advance,
    Pete

    Hi Peter,
    As you are having issue with SDK's.
    I would suggest you to post your question in
    Business Objects SDK Application Development » [Legacy Application Development SDKs|;
    That forum is monitored by qualified technicians and you will get a faster response there. Also, all  SDK queries remain in one place and thus can be easily searched in one place.
    Thank you for your understanding,
    Shweta

  • Installation of Golf Program requires uninstalling Microsoft SQL 2005 and installing SQL 2000

    I am running Win 7 and about to purchased a new computer with Win 8.1. 
    The USGA wrote a Tournament Program which is used nationwide called TPP (Tournament Pairing Program).  It was developed prior to XP but it is updated every time you run the update.  It runs on XP without any adjustments.  To load the program
    on Win 7 or Win 8 you are instructed to remove Microsoft SQL Server 2005, which I did.  The program loads SQL 2000 when it is installed.  I am concerned when I uninstall the TPP program that it will also uninstall SQL 2000 (which it installed) and
    then there will be no SQL server on my Win 7.
    I was going to make sure that I could install the TPP program on Win 8 (before buying another computer) by installing it on a friends new Win 8.1 computer.  But I am concerned about removing the preinstalled SQL Server program.
    1) How does one get the original Microsoft SQL Server back once it has been removed and the recycle bin has been emptied?  Does the SQL program even get sent to the recycle bin when it is removed?
    2)  Is there any harm done by removing the original SQL program be it 2005 or a new one?

    SQL 2000 is not supported on Windows 7.
    http://support.microsoft.com/kb/2028963/en-us
    whenever you uninstall SQL Server, databases files are not deleted. So you can move them to safe location. if they are delete by you then you have very less chances to recover the data.
    Balmukund Lakhani
    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog |
    Team Blog | @Twitter
    | Facebook
    Author: SQL Server 2012 AlwaysOn -
    Paperback, Kindle

  • 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

  • Custom DTS package migration from BPC 4.2 ,SQL 2000 to BPC 7.0 M , SQL 2005

    Is there any changes required in the custom dts package when migration from BPC 4.2 , sql 2000 Environment to bpc 7.0 , SQL 2005/2008  Environment.
    or
    Please suggest process for migrating  custom dts package from BPC 4.2 ,SQL 2000 Envirnment to BPC 7.0 ,SQL 2005/2008 Environment

    When you say "custom dts package" that can mean many different things. What type of customization has been done?
    There are a few BPC-related features which changed from 4.2, which must be manually adjusted, if you're using those features.
    But SQL itself also changed dramatically in moving from SQL 2000 to 2005. So if your customer's packages are heavily customized around SQL 2000, this may require substantial re-work.
    The only migration process for custom DTS packages -- that I'm aware of -- is to use the SQL 2005 migration tool in SSIS, see how much it messed up, and then fix everything else that's still broken.
    But there also may be opportunities to improve the package overall. SQL 2005 has a lot of great new features in SSIS, over what was there in SQL 2000.
    I haven't started working with SQL 2008 yet, so I can't say what complexity there is in upgrading DTS packages from 2005 to 2008. From what I read in the BPC 7 release notes, it sounds like it's a very minor upgrade, compared to the jump from 2000 to 2005.

  • Restoration at sql 2005 from sql 2000 backup.

    Hi experts,
    Is it possible to restore a backup taken from sql 2000 database to sql 2005 database?
    And how about attaching datafiles of sql2000 into sql 2005 server?
    Thanks and Regards,
    Amit Jana.

    > Is it possible to restore a backup taken from sql 2000 database to sql 2005 database?
    Yes its possible.
    > And how about attaching datafiles of sql2000 into sql 2005 server?
    Same method of attach/deattach.
    But recommanded you first install 2000 instance restore database and do inplace sql 2005 upgrade.
    Why you can't follow recommanded mothed ?
    Regards,
    Nikunj Thaker

Maybe you are looking for