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

Similar Messages

  • 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

  • Moving sql server 2000 to sql server 2014

    Moving sql server 2000 to sql server 2014. Could someone please give me steps to move everything from sql 2000 one server to sql 2014. I have 2 instance on sql 2000. 8 databases on each of them. On both instances we have store procedure and jobs.

    i think your SQL Server 2000 is hosted on old Windows server version so based on that you should prepare new environment for SQL Server 2014 from Win Server 2012 Sp1 and SQL Server 2014 and build your clusters then start your Migration from Old Servers to
    new servers and here below is 10 configurations outlines that you should look after carefully for any DB consolidation or migration from a server to  a server and indeed they represent unique potentials for your DB Consolidation /migration service that
    can leverage distinctly your service quality and shape you very well in front of your customers:
    1-      Backup DBs and restore DBs with ZERO down time and ZERO data loss in the same time …Awesome …!
    2-      Cloning all DB special features that are not covered by backups and restores such as :
    RCSI (Read committed snapshot isolation level using row versioning)
    Service brokers
    Encryption keys and certificates
    3-      Cloning identically all SQL logins with their mapped DB users including their passwords (if SQL authenticated logins ) and privileges on both server and DB levels .
    4-      Copying .rdl and .rds files between different versions of reporting services where backup and restore reportserver and reportservertemp DBs is not an option
    5-      Cloning all special Jobs like certain business jobs configured to perform some business stuff .
    6-      Cloning all mail profiles with their mail accounts
    7-      Cloning all Linked server + Aliases might be used inside old DB servers
    8-      Cloning some server configurations like CLR ,CPU parallelism, Replication size , Network packet size , optimize for ad hoc workloads
    9-      Cloning all Replications configurations for publishers and subscribers
    10-   Cloning all DTC configurations for both local and clustered DTC services
    Follow the below links to know the steps by the scripts:
    http://sqlserver-performance-tuning.net/?p=5262
    http://sqlserver-performance-tuning.net/?p=5359
    http://sqlserver-performance-tuning.net/?p=5398
    http://sqlserver-performance-tuning.net/?p=5415
    http://sqlserver-performance-tuning.net/?p=5458
    Mustafa EL-Masry
    Principle Database Administrator & DB Analyst
    SQL Server MCTS-MCITP
    M| +966 54 399 0968
    MostafaElmasry.Wordpress.com

  • Why does my font/text change when I switch from Classic 3D to Ray traced 3D in After Effects?

    My font/text changes when I switch from Classic 3D to Ray traced 3D. Why is it doing this? Also, I cant get the font/txt to look the same after I switch from Classic to Ray traced. How can I get it to look the same?

    I am pretty new to After Effects so I hope it's not my inexperience that's causing the problem. (It probably is)
    I just updated to the most current version of AE.
    I am on a mac pro late 2013 12GB 6 core. Running OSX 10.9.4
    Okay so after looking at it a little closer, I think the color is what mostly changes. The first screenshot is the what the text look like with Classic 3D and the second screenshot is what it looks like after I change it to Ray traced 3D. Also under the "Mode" section..the pull down that says "Normal" disappears. I'm wondering why the font color is changing?

  • Switch from MS exchange to OS X server 10.5.4 running mail

    we have switched from MS Exchange server 2003 to mac os x 10.5.4 server.
    I have set up mail on this. The client connects ok, and the server gets mail, but no mail gets through the server, neither in nor out.
    Reason: Remote SMTP server has rejected address
    Diagnostic code: smtp;554 5.7.1 <[email protected]>: Relay access denied
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = all
    mail_owner = _postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    messagesizelimit = 10485760
    mydestination = $myhostname,localhost.$mydomain,localhost,metropolis.local
    mydomain = metropolis.no
    mydomain_fallback = localhost
    myhostname = bigapple.metropolis
    mynetworks = 127.0.0.0/8,192.168.168.0/24,127.0.0.0/24
    newaliases_path = /usr/bin/newaliases
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    relayhost =
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = _postdrop
    smtpdpw_server_securityoptions = gssapi
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpduse_pwserver = yes
    unknownlocal_recipient_rejectcode = 550

    In Server Admin -> Mail -> Settings change the hostname from bigapple.metropolis to bigapple.metropolis.no
    Next add metropolis.no to local host aliases in Server Admin -> Mail -> Settings -> Advanced -> Hosting
    HTH,
    Alex

  • Connection with SQL Server 2000 to SQL Developer 1.2 Migration Workbench

    Hi all,
    I keep getting the following error with setup for SQL Developer 1.2 Migration Workbench connection to SQL Server 2000 database:
    "Status: Failure -Network error IOException: Connection refused:connect"
    I can access the Microsoft SQL Server 2000 database with username
    and password using Enteprise Manager. However for some odd
    reason the Oracle SQL Developer 1.2 cannot connect to it.

    I was having this problem too. I'll mangle this explanation, but Our SQLServer instance was on a local server with some named DNS something. So, to get to the server, we used theservername.outdomain instead of an IP. We could never get it to connect through the named server. We got an SQLServer instance going on a server that we could connect to through a regular IP, and it connected just fine.
    Also, are you using the JTDS driver, or microsofts driver? We have only been able to connect with the JTDS driver. http://jtds.sourceforge.net/

  • SQL Upgrade 2000 to SQL 2005

    We are upgrading to new server and installing SQL 2005.  Using Crystal Server 10.  Where can I find a step by step?  Can I just backup Business Objects Database, install the app on the new server, restore the database to SQL 2005?
    Thanks,
    SS

    Hi Samuel
    You can refer the below link for more information on SQL Server 2005 upgrade.
    [http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlupgrd.mspx#top]
    Regards
    Girish.

  • Upgrade SQL From the SQL Server 2000 to SQL Server 2008

    hello:
    I am running the following query. This query is based on SQL server 2008. POIShare is a view which is created by the table.
    "select PoiShare.AddressCode,REPLACE(PoiShare.NameSpell,' ','') as NameSpell,PoiShareOffset.Offset from PoiShare, PoiShareOffset where POIShare.AddressCode & 0xFF000000 = %COUNTRY_ADCODE% and PoiShare.POIID = PoiShareOffset.POIID order by PoiShare.AddressCode,PoiShare.NameSpell"
    I'm getting the following result.
    3188785409 "папа,мама,я"
    791241
    3188785409 01кафе
    0
    3188785409 007
    5767272
    3188785409 03
    4790808
    3188785409 02lounge
    19
    3188785409 03аптека
    4791813
    3188785409 03аптека
    4791805
    3188785409 01сервис
    1246782
    "PoiShare.NameSpell" is not sorted. I try to solve this problem.but It doesn't work.
    I tried some ways.
    1.Sort all of the field
    2.Using "COLLATE Cyrillic_General_CI_AI_KS_WS" to "NameSpell"
    3.Create index  for "NameSpell"
    4.Using "cast(replace(PoiShare.NameSpell,',','') as bigint)",But SQL returned an error
    5.Install SQL SP1
    any help is greatly appreciated.

    SELECT * FROM <<VIEW>>
    ORDER BY <<COLUMN>>
    The query above work fine in SQL Server 2008. NameSpell has already been sorted, thank you.

  • In place upgrade from Windows Server 2000 to Windows Server 2003 ADS

    Hi...is anyone aware of any issues with performing an in place upgrade from Windows 2000 Server to 2003 Server, which is currently running ESSBASE? Please advise, if you have any information. Thank you.

    You can post your question in ESSBase forum
    Essbase

  • Changes required for Migration from CR 8.5 to CR 11

    Dear All,
      We have successfully migrated all the reports which were created in CR 8.5 to CR 11. But those same reports developed in CR 8.5 are called through .exe which has been built with Microsoft Visual Studio .NET 2003. The old reports of CR 8.5 is working fine. while we are unable to open CR 11 reports through .exe. It says DLL missing. I guess some higher version of p2sodbc.dll and some more required.
    Can you please help me out.
    Warm regards,
    Santosh Kumar Prashant

    If you have VS .NET 2003, then all you need to do is install CR XI Developer. I would not recommend using the RDC in.NET for two basic reasons:
    1) The RDC has not been tested in .NET (thus no escalation is available for any fix issues)
    2) The RDC has been retired in CR 12. This may have implications for the lifecycle of your project...
    To see how to use the RDC in .NET, check out the article [Using the Report Designer Component in Microsoft Visual Studio .NET|https://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/f0751a7f-a81d-2b10-55a0-e6df0e1bab6d&overridelayout=true]
    My recommendation would be to use the CR assemblies for .NET. The following resources should get you going:
    [Sample applications|https://wiki.sdn.sap.com/wiki/display/BOBJ/CrystalReportsfor.NETSDK+Samples]
    [Crystal Reports For Visual Studio 2005 Walkthroughs|https://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/2081b4d9-6864-2b10-f49d-918baefc7a23&overridelayout=true] (most of the concepts will apply to .NET 2003)
    [Advanced use of Crystal Reports for Visual Studio .NETu2019s feature set and object model|https://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/702ab443-6a64-2b10-3683-88eb1c3744bc&overridelayout=true]
    Developer libraries:
    https://boc.sdn.sap.com/developer/library
    http://devlibrary.businessobjects.com
    Also, ensure you apply the latest CR XI r1 [Service Pack|https://smpdl.sap-ag.de/~sapidp/012002523100006008952008E/crXIwin_sp4.zip]
    Ludek

  • Cannot upgrade a Server 2000 VM to Server 2003

    Hello!
    I have a Server 2008 R2 Enterprise SP1 Hyper-V server, and I have a VM of an ancient Windows 2000 Advanced Server. I need to test an in-place upgrade of that VM to Server 2003 Enterprise for a legacy app.
    When I attempt the in-place upgrade, it reboots normally once about half way through the upgrade and goes back into the setup, then gets to the final stages, reboots, and then I get a BSOD with 0x0000007B error, inaccessible boot device.
    Has anyone here successfully done an in-place upgrade inside of a VM going from 2000 to 2003?
    A fresh installation of 2003 into a VM works fine.
    I cannot wrap my head around why a perfectly running 2000 VM would suddenly not be able to find the boot device when upgraded to 2003. If a fresh install of 2003 recognizes the VM and boots properly, why wouldn't it do the same in an upgrade in a VM?
    I am trying other methods and have been Googling it for hours.
    Thank you!
    Gregg Hill

    OK, I swear I don't drink booze or do drugs, but I think I may need to start! I am going to go straight to crack.
    I just followed the same steps I have done five times before (definition of insanity?!), and this time, the 2000 to 2003 upgrade worked.
    - Started with a fully-patched 2000 Advanced Server VM.
    - Removed the Integration Services and rebooted.
    - Started the 2003 upgrade from within the VM.
    - Got the same black screen that I was getting before with "A disk read error occurred, "Press Ctrl-Alt-Del to restart" on the screen after
    the first reboot
    - Set the VM to boot from the CD first, then when it said "Hit any key to boot from CD," I hit a key. At that point it asked if I wanted
    to continue the upgrade. Making that choice lets it continue.
    - Prior to this installation, the VM would reboot half way through the installation steps, then start back up and finish the installation.
    After the final reboot, it would BSOD with the 7B error. This time, it did NOT reboot at the half way mark.
    - This time, for reasons unknown, the same exact steps successfully installed the upgrade.
    I am going to back up this VM and try it again. Yes, I am a glutton for punishment, but I need to know WHY it worked this time.
    Strange stuff!

  • BO 6.5 switching from SQL Sql Server 2000 to 2005

    Need information for BO 6.5 on issues switching from Sql Server 2000 to Sql Server 2005.
    Thanks in advance for any information!

    If you're migrating the Repository database as well from SQL 2000 to SQL 2005, you need to also to update the security files by taking the steps below:
    1. Stop the server
    2. Rename the existing security files (bomain.key and bomain.lsi)
    3. Run the Safe Recovery to regenerate a new bomain.key
    4. Run the Scan, Repair and Compact of the Repository
    5. Copy the new bomain.key to the locdata located at u2026\nodes\<server>\<cluster>\locdata
    Regards,
    Jeff

  • JDBC connection for SQL Server 2000

    How to connect SQL Server 2000 from java?
    If i can get any sites where i can get examples also fine.
    Thanks in advance
    Praveen.

    Developer's Daily  Java Education 
      front page | java | perl | unix | DevDirectory 
      Front Page
    Java
    Education
    Pure Java
       Articles
    JDBC 101: How to connect to an SQL database with JDBC
    Introduction
    If you're interested in connecting your Java applets and applications to standard SQL databases like Oracle, Informix, Sybase, and others, JDBC is your ticket to paradise.  The combination of Java's JDBC and standard SQL makes a simple and powerful database solution. JDBC makes the simple things easy -- without making the complex tasks too difficult either.
    In this first article in our series, we'll show you step-by-step how to establish a connection from your Java programs to an SQL database using JDBC. In the process we'll show you how to connect to two different databases -- Mini SQL (mSQL), and Interbase -- just so you can see how the code changes when you switch from one database to another.
    Obtaining the JDBC driver
    Before you start working with JDBC, you'll need a copy of the Java JDK. If you don't have it already, you can get the JDK for free at Sun's Java web site, or it will also be included with many IDE's that you can purchase, such as JBuilder or Visual Cafe.
    Once you have the JDK, the next thing you need to do is to get the correct JDBC driver for your database. In most cases the JDBC driver will be provided by your database vendor. For instance, if you purchase the Interbase database, the driver will be provided with the software, or you can obtain the most recent version at http://www.interbase.com/.
    (An exception to this rule is Mini SQL, or mSQL. Because it's a very low-cost database, the JDBC driver has actually been developed by a separate group of people, led by George Reese at imaginary.com. You can download the mSQL JDBC driver from the imaginary.com web site.)
    Once you have the correct JDBC driver for your database, install it according to the instructions that came with it. Installation instructions will vary somewhat for each vendor.
    Establishing a connection is a two-step process
    Once you have the correct JDBC driver installed, establishing a connection from your Java programs to your SQL database is pretty easy.
    Regardless of whether you're trying to connect to Oracle, Sybase, Informix, mSQL, or Interbase (or any other JDBC data source), establishing a connection to an SQL database with Java JDBC is a simple two-step process:
    Load the JDBC driver.
    Establish the connection.
    We'll show you two examples just so you can see how easy it is, and how little the code changes when you migrate from one database server to another.
    A Mini SQL Example
    Listing 1 provides the full source code required to establish a connection to a mSQL database on a server named "www.myserver.com".
      //  Establish a connection to a mSQL database using JDBC. 
    import java.sql.*; 
    class JdbcTest1 { 
        public static void main (String[] args) { 
            try { 
                // Step 1: Load the JDBC driver. 
                Class.forName("com.imaginary.sql.msql.MsqlDriver"); 
                // Step 2: Establish the connection to the database. 
                String url = "jdbc:msql://www.myserver.com:1114/contact_mgr"; 
                Connection conn = DriverManager.getConnection(url,"user1","password");  
            } catch (Exception e) { 
                System.err.println("Got an exception! "); 
                System.err.println(e.getMessage()); 
      Listing 1: This source code example shows the two steps required to establish a connection to a Mini SQL (mSQL) database using JDBC. 
    An Interbase Example
    Listing 2 provides the full source code required to establish a connection to an Interbase database. In this example, we're connecting to a local Interbase server (i.e., the server is running on the same PC that we're running the Java code on).
      //  Establish a connection to an Interbase database using JDBC. 
    import java.sql.*; 
    class JdbcTest1 { 
        public static void main (String[] args) { 
            try { 
                // Step 1: Load the JDBC driver. 
                Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); 
                // Step 2: Establish the connection to the database. 
                String url = "jdbc:odbc:contact_mgr"; 
                Connection conn = DriverManager.getConnection(url,"user1","password");  
            } catch (Exception e) { 
                System.err.println("Got an exception! "); 
                System.err.println(e.getMessage()); 
      Listing 2: This source code example shows the two steps required to establish a connection to an Interbase database using JDBC. 
    What's the difference?
    The difference between the two source code listings is very small, so we highlighted them in a dark blue color. The only difference between connecting to the two databases is:
    The name of the JDBC driver.
    The URL used to connect to the database.
    Everything else in the two source code listings -- except for the comment at the top -- is identical. Here's a slightly more detailed discussion of the two differences:
    1. The JDBC Driver
    The name of the JDBC driver will be supplied to you by your database vendor. As you can see in the class.forName() statements, these names will vary. In the first case we're using the mSQL-JDBC driver. In the second case we're using the JDBC-ODBC Bridge driver supplied with the Interbase server.
    2. The URL
    The syntax of the DriverManager.getConnection() method is:
    DriverManager.getConnection(String url, String username, String password);
    The username and password are the normal names you use to log into your database. The URL you use will again vary with the database you use. In both examples shown, we're establishing a connection to a database named contact_mgr. (We'll use this database for all of our examples in this series of JDBC articles.)
    If you stick with standard SQL commands, it can be very easy to switch from one database server to another. In fact, I've heard from several developers who are using mSQL to prototype their software (because it's so inexpensive), and then switching to another commercial vendor when it's time to take their product "live".
    Conclusion
    Establishing a connection to an SQL database with Java JDBC is a simple, two-step process. The process is nearly identical for all SQL databases, and the only real differences are (a) the driver name, and (b) the URL used to connect to the database. Your database vendor will provide this information in their documentation.
    Resources mentioned in this article
    Here are a few links to resources we mentioned in this article:
    Interbase
    The Mini SQL (mSQL) database
    The mSQL-JDBC driver at imaginary.com
      [an error occurred while processing this directive]
     

  • SQL server 2012 link server 2000

    I am trying to link an SQL Server 2000 to SQL Server 2012.
    From the management studio i am giving the configuration below
    Other data source
    Provider --> SQL Server Native Client 10.0
    Product name: SQLSERVER
    Data Source: machines_ip/Servername
    Provider string: (null)
    Catalog: (null)
    Security Tab
    Be made using this security context: (credentials)
    Server Option Default except of changing RPC out to True
    I get the error 7302 but and help returns no results:
    There is no additional information about this issue in the Error and Event Log Messages or Knowledge Base databases at this time. You can use the links in the Support area to determine whether any
    additional information might be available elsewhere.
    What am i missing?

       can check with 
    In SQL Server Enterprise Manager, open \Server Objects\Linked Servers\Providers, right click on the  provider, select
    properties and check the "Allow inprocess" option and set 1. Recreate your linked server and test again.
    13down
    vote
    In SQL Server Enterprise Manager, open \Server Objects\Linked Servers\Providers, right click on the OraOLEDB.Oracle provider, select properties and check the "Allow inprocess" option. Recreate your linked server
    and test again.

  • SQL Server 2000 std Report Performance Issue

    Dear All,
    I have a VB based desktop application with back end MS SQL server 2000 database with server machine ibmx5650 with specs intel xeon 2.7GHz (24 CPU's) & 24GB RAM.
    There are two things i need help:
    Recently we have upgrade the SQL server from 2000 personal edition to the 2000 standard edition. There comes a problem with one of the Report in the application. The report took almost 30 mins previously in SQL 2000 personal edition.But after the upgrade
     to Standard edition we are unable to view report before 3 hours even sometimes it doesn't appear after several hours.
    Secondly for brief testing i have installed the personal edition on a simple PC rather then a server PC specs are corei5 & 4 GB of RAM. The same report is generated in only 15 mins from the application with this desktop machine as DB server.
    Please help me out i have gone through all SQL Server & system performance log of my server machine everything is normal but the report is taking too long & i can only generate that report from personal edition.
    Is there the difference due the higher corei5 processor in desktop machine or there is any other issue behind this.
    Your prompt response is highly appreciated.
    Regards,
    Rashid Ali

    Hello,
    SQL Server 2000 is not support since 2013. Please upgrade to SQL Server 2012 to get better performance and support.
    Thanks for your understanding and support.
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

Maybe you are looking for