SQL 2000 export to discoverer

Does anybody know how to export data from SQL 2000 to an EEX file?
I want to create an EUL for discoverer.
I already created an oracle database and want to import the EEX file to discoverer.
Is there a tool for this export?

Hi Russ
An extra database means extra license fee for Oracle - I suspect this is the more likely reason why direct connectivity is no longer allowed. Maybe I'm being too harsh on Oracle but this is what always goes through my mind when I see something like this.
Its something similar to the push for Siebel - which does have better features than Discoverer (although it wouldn't if Oracle BI group wasn't being run by ex-Siebel employees these days) and - oh yes - there is the small fact that it costs 5 to 6 times more than Discoverer. The funny is that none of my clients, and I have hundreds, have expressed any intention of investing that sort of money when they get over 90% of what they need from Discoverer. All my clients want is Discoverer. How we all wish that Oracle would invest a little into the relational side and make it do some of the things that Siebel can. So what about you? Do you have any takers for Siebel?
In Disco 3 and 4, as you say, it was dead easy to do remote database connectivity because all you did on the connect line was prefix the database with ODBC: Oh the good old days :-)
Best wishes
Michael

Similar Messages

  • Migrate 4.5B + SQL 2000 on new Hardware

    Hi guys.
    Can I make a homogeneous system copy SAP R/3 4.5B (Windows 2000 + sql 2000) in a source system and run the import in the target system on (Windows 2003 + sql 2000)  in 64-bit platform without the migration from 32 bits to 64 bits?
    I can be running SAP R/3 4.5B on 64 bit platform, without the migration of SAP R/3  to 64 bits.
    The client wants to migrate their platform to 4.5B on new harwdware, but the next year to migrate to ECC 6.0, but at this time without making the change to 64 bits, because 45B is not supported in 64 bits.
    I would like to know that I can offer tips.
    Thanks a lot.
    dcardena.

    Check the note 960769 : Windows Migration 32 bit to 64 bit
    you need to check compatibility of MS SQL 2000 on Windows 2003 64 bit servers, Microsoft supports SQL 2000 SP4 on 64 bit servers.
    SAP 4.5B can be run on 32 bit mode.
    Also, you need to check with SAP whether it is supported for productive operation or only for "upgrade" purpose.
    Also,look into SAP note 666805: MS SQL Server Migrating from 32 bit to 64 bit.
    It describes the attach/detach procedure to migrate to 64 bit server. It can avoid the import/export process.

  • 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

  • SQL 2000 - Blocking Happening again and again

    Hi  guys..
    on sql 2000 ..from today morning blocking keep happening again and again even though killed SPID .. Reastarted SQL and app server. any one has idea what will be good action item?
    also like to know scripts for sql 2000 gives detailed information about which query is blocking .
    In sp_who2 shows IIS program name as blocking 
    thanks
    Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach A.Shah

    Hello,
    Refer to below link
    http://support.microsoft.com/kb/224453/en-gb
    If you have Database with high concurency some blocking is inevitable ,moreover if blocking is there for few seconds its not an issue a long block is a issue though.Below query will give blocking information
    select * from sys.sysprocesses where blocked <> 0
    To check lead blocker
    IF EXISTS ( SELECT 1 FROM master.dbo.sysprocesses WHERE blocked <> 0 )
    SELECT spid,
    status,
    loginame = SUBSTRING(loginame, 1, 30),
    hostname = SUBSTRING(hostname, 1, 12),
    blk = CONVERT(char(4), blocked),
    open_tran,
    dbname = SUBSTRING(DB_NAME(dbid),1,10),
    cmd,
    waittype,
    waittime,
    last_batch
    FROM master.dbo.sysprocesses NOLOCK
    WHERE spid IN (SELECT blocked FROM master.dbo.sysprocesses)
    AND blocked = 0
    ELSE
    SELECT 'No blocking found!'
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Sql 2000 database role

    Hi ,
    I want to grant execute permission to all SP's in SQL 2000  database, when I tried to create a db_execprocs role it is throwing an error near ROLE, and when I googled  I have found a script as 
    CREATE PROCEDURE dbo.spGrantExectoAllStoredProcs @user ABC\venkat
    AS
    -- Object Name: spGrantExectoAllStoredProcs
    -- Author: Edgewood Solutions
    -- Development Date: 03.19.2007
    -- Called By: TBD
    -- Description: Issue GRANT EXEC statement for all stored procedures 
    -- based on the user name that is passed in to this stored procedure
    -- Project: SQL Server Security
    -- Database: User defined databases 
    -- Business Process: SQL Server Security
    -- Num | CRF ID | Date Modified | Developer | Description
    -- 001  | N\A     | 03.15.2007    | Edgewood | Original code for the GRANT 
    -- EXEC process
    SET NOCOUNT ON
    -- 1 - Variable declarations
    DECLARE @CMD1 varchar(8000)
    DECLARE @MAXOID int
    DECLARE @OwnerName varchar(128)
    DECLARE @ObjectName varchar(128)
    -- 2 - Create temporary table
    CREATE TABLE #StoredProcedures
    (OID int IDENTITY (1,1),
    StoredProcOwner varchar(128) NOT NULL,
    StoredProcName varchar(128) NOT NULL)
    -- 3 - Populate temporary table
    INSERT INTO #StoredProcedures (StoredProcOwner, StoredProcName)
    SELECT u.[Name], o.[Name]
    FROM dbo.sysobjects o
    INNER JOIN dbo.sysusers u
    ON o.uid = u.uid
    WHERE o.Type = 'P'
    AND o.[Name] NOT LIKE 'dt_%'
    -- 4 - Capture the @MAXOID value
    SELECT @MAXOID = MAX(OID) FROM #StoredProcedures
    -- 5 - WHILE loop
    WHILE @MAXOID > 0
    BEGIN 
     -- 6 - Initialize the variables
     SELECT @OwnerName = StoredProcOwner,
     @ObjectName = StoredProcName
     FROM #StoredProcedures
     WHERE OID = @MAXOID
     -- 7 - Build the string
     SELECT @CMD1 = 'GRANT EXEC ON ' + '[' + @OwnerName + ']' + '.' 
     + '[' + @ObjectName + ']' + ' TO ' + '[' + ABC\venkat + ']'
     -- 8 - Execute the string
     -- SELECT @CMD1
     EXEC(@CMD1)
    -- 9 - Decrement @MAXOID
    SET @MAXOID = @MAXOID - 1
    END
    -- 10 - Drop the temporary table
    DROP TABLE #StoredProcedures
    SET NOCOUNT OFF
    GO
    this too is throwin an error as:
    Msg 170, Level 15, State 1, Procedure spGrantExectoAllStoredProcs, Line 1
    Line 1: Incorrect syntax near '\'.
    Msg 170, Level 15, State 1, Procedure spGrantExectoAllStoredProcs, Line 52
    Line 52: Incorrect syntax near '\'.
    Can someone help me with this.
    I just need to grant execute permission on all SP's  to 1 database only.
    Thanks.

    First create the procedure and then call the procedure with parameter.
    Try this 
    CREATE PROCEDURE dbo.spGrantExectoAllStoredProcs @user varchar(20)
    AS
    -- Object Name: spGrantExectoAllStoredProcs
    -- Author: Edgewood Solutions
    -- Development Date: 03.19.2007
    -- Called By: TBD
    -- Description: Issue GRANT EXEC statement for all stored procedures
    -- based on the user name that is passed in to this stored procedure
    -- Project: SQL Server Security
    -- Database: User defined databases
    -- Business Process: SQL Server Security
    -- Num | CRF ID | Date Modified | Developer | Description
    -- 001 | N\A | 03.15.2007 | Edgewood | Original code for the GRANT
    -- EXEC process
    SET NOCOUNT ON
    -- 1 - Variable declarations
    DECLARE @CMD1 varchar(8000)
    DECLARE @MAXOID int
    DECLARE @OwnerName varchar(128)
    DECLARE @ObjectName varchar(128)
    -- 2 - Create temporary table
    CREATE TABLE #StoredProcedures
    (OID int IDENTITY (1,1),
    StoredProcOwner varchar(128) NOT NULL,
    StoredProcName varchar(128) NOT NULL)
    -- 3 - Populate temporary table
    INSERT INTO #StoredProcedures (StoredProcOwner, StoredProcName)
    SELECT u.[Name], o.[Name]
    FROM dbo.sysobjects o
    INNER JOIN dbo.sysusers u
    ON o.uid = u.uid
    WHERE o.Type = 'P'
    AND o.[Name] NOT LIKE 'dt_%'
    -- 4 - Capture the @MAXOID value
    SELECT @MAXOID = MAX(OID) FROM #StoredProcedures
    -- 5 - WHILE loop
    WHILE @MAXOID > 0
    BEGIN
    -- 6 - Initialize the variables
    SELECT @OwnerName = StoredProcOwner,
    @ObjectName = StoredProcName
    FROM #StoredProcedures
    WHERE OID = @MAXOID
    -- 7 - Build the string
    SELECT @CMD1 = 'GRANT EXEC ON ' + '[' + @OwnerName + ']' + '.'
    + '[' + @ObjectName + ']' + ' TO ' + '[' + @user + ']'
    -- 8 - Execute the string
    -- SELECT @CMD1
    EXEC(@CMD1)
    -- 9 - Decrement @MAXOID
    SET @MAXOID = @MAXOID - 1
    END
    -- 10 - Drop the temporary table
    DROP TABLE #StoredProcedures
    SET NOCOUNT OFF
    GO
    dbo.spGrantExectoAllStoredProcs 'abc\venkat'
    OR
    directly execute the below script
    Change the @user parameter with valid account
    DECLARE @User Varchar(20)
    DECLARE @CMD1 varchar(8000)
    DECLARE @MAXOID int
    DECLARE @OwnerName varchar(128)
    DECLARE @ObjectName varchar(128)
    SET @user='abc\venkat'
    -- 2 - Create temporary table
    CREATE TABLE #StoredProcedures
    (OID int IDENTITY (1,1),
    StoredProcOwner varchar(128) NOT NULL,
    StoredProcName varchar(128) NOT NULL)
    -- 3 - Populate temporary table
    INSERT INTO #StoredProcedures (StoredProcOwner, StoredProcName)
    SELECT u.[Name], o.[Name]
    FROM dbo.sysobjects o
    INNER JOIN dbo.sysusers u
    ON o.uid = u.uid
    WHERE o.Type = 'P'
    AND o.[Name] NOT LIKE 'dt_%'
    -- 4 - Capture the @MAXOID value
    SELECT @MAXOID = MAX(OID) FROM #StoredProcedures
    -- 5 - WHILE loop
    WHILE @MAXOID > 0
    BEGIN
    -- 6 - Initialize the variables
    SELECT @OwnerName = StoredProcOwner,
    @ObjectName = StoredProcName
    FROM #StoredProcedures
    WHERE OID = @MAXOID
    -- 7 - Build the string
    SELECT @CMD1 = 'GRANT EXEC ON ' + '[' + @OwnerName + ']' + '.'
    + '[' + @ObjectName + ']' + ' TO ' + '[' + @user + ']'
    -- 8 - Execute the string
    -- SELECT @CMD1
    EXEC(@CMD1)
    -- 9 - Decrement @MAXOID
    SET @MAXOID = @MAXOID - 1
    END
    -- 10 - Drop the temporary table
    DROP TABLE #StoredProcedures
    --Prashanth

  • SQL 2000 LINKED SERVER ERROR 7303 WITH SQL 2012 ON WINDOWS SERVER 2012 R2

    Hi all,
    I have a problem with SQL Server 2012 and a linked server for SQL 2000 database.
    System specification:
    Windows server 2012 64 bit
    SQL SERVER 2012 64 bit
    REMOTE SERVER SQL 2000 32 bit
    I've installed sql native client 32bit,create a SYSTEM DSN odbc connection with "SQL Server" driver named "MYSERVER".
    Create a linked server with the query below in SQL 2012:
    EXEC master.dbo.sp_addlinkedserver @server =N'MYSERVER', @srvproduct=N'MYSERVER', @provider=N'MSDASQL', @datasrc =N'MYSERVER', @location=N'System';
    EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'MySERVER',@useself=N'True',@locallogin=NULL,@rmtuser=NULL,@rmtpassword=NULL
    GO
    but when i browse the linked server i receved error 7303.

    You need 64-bit MSDASQL. It is the bitness of the server you are connecting from that matters. 64-bit executables cannot hook into 32-bit DLL.
    However, I suspect that you will not get things to work anyway. At least I have not seen anyone this far who has been able to set up a linked server from SQL 2012 to SQL 2000. I know that when I tried this, the following providers had this result:
    SQLNCLI11 - does not support connections to SQL 2000.
    SQLNCLI10 - failed with some obscure message that I don't recall.
    SQLNCLI - Don't recall that the problem was here.
    SQLOLEDB - SQLOLEDB is always replaced with the most recent version of SQLNCLI, so this fails because of lack of support.
    I don't think I got through all version of the ODBC drivers, though.
    Erland Sommarskog, SQL Server MVP, [email protected]

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

  • How to upload sap r/3 table data to ms-sql 2000?

    Dear Friends
    any one can help me out step by step to upload sap r/3 table data to ms-sql 2000.
    Thanks in advance

    hi
    good
    go through this link
    http://www.itcserver.com/blog/2006/06/29/data-transfer-methods/
    thanks
    mrutyun^

  • 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

  • How to spool the result of an query into a file in sql 2000

    Hi All,
    I have an SQL query which iterates through number of times for checking on some conditions and will return results each time. I wants to save the results into an different xml file each time. I tried using below query:
    exec xp_cmdshell 'bcp "use Mimsadaptorlogs; select top 10 * from log order by logdate" queryout "D:\cdr_cg.xml" -T -c -t,'  ---> Its not working as expected.
    I got the Below output:
    NULL
    Starting copy...
    SQLState = 01000, NativeError = 5701
    Warning = [Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'MIMSAdaptorlogs'.
    NULL
    10 rows copied.
    Network packet size (bytes): 4096
    Clock Time (ms.): total       62
    NULL
    Could you anuone please suggest me on this.......
    Thanks and Regards, Bala

    You will need to write a client program to do this. SQL Server is not intended for writing files. People still do it by calling BCP through xp_cmdshell, but this is a dubious practice. Better is to write a CLR stored procedure for the task. However, you
    are on SQL 2000, and the CLR support was added in SQL 2005. Furthermore, there is no XML type in SQL 2000, and the only way to generate XML is with the FOR XML clause. But this output is not well understood by BCP. Then I try: [code} bcp "SELECT * FROM Northwind..Customers
    FOR XML RAW" queryout slask.bcp -c -T [/code] on SQL 2000, I get [code] 11 rows copied. [/code] which is complete hogwash, because there are 91 rows in that table, and the output should be a single XML document, and the output looks like this: [code] <row
    CustomerID="ALFKI"... Bouchers" City="Marseil... tomerID="DUMON" Company... 0.32.21.21" Fax="40.32.... los Hern ndez" ContactT... n Steel" ContactTitle="... e" ContactTitle="Market... ="Salzburg" PostalCode=... " Phone="(21) 555-3412"... ty="Charleroi" PostalCo...
    <row CustomerID="WARTH"... [/code] I have truncated the output on the right side, but the left side is authentic. It really is that bad.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Hi Pls help me, How to work with SQL 2000 Database

    I have database using SQL 2000, How to connect and work with SQL 2000 Database. thanks

    Log on to www.SQLite.org that may help you.
    Using the Sqlite3.dll and after customizing your code with SQLite3.h you can read and write on to that DB.

  • Please Help!!!!! Problem Migrating from sql 2000 stored procedure to PL/SQL

    I have used a tool to convert my sql 2000 stored procedure to Oracle 10g PL/SQL, here is an example
    SQL 2000 Stored Procedure
    CREATE PROCEDURE [GetEmployees]
    AS
    Select * from EMPMST ORDER BY emp_name
    GO
    After Transformation i got 2 files, one was a procedure and other a package
    CREATE OR REPLACE PACKAGE GLOBALPKG
    AS
         TYPE RCT1 IS REF CURSOR;
         TRANCOUNT INTEGER := 0;
         IDENTITY INTEGER;
    END;
    CREATE OR REPLACE PROCEDURE GetEmployees
         RCT1 IN OUT      GLOBALPKG.RCT1
    AS
    BEGIN
         OPEN RCT1 FOR
         SELECT *
         FROM EMPMST
         ORDER BY emp_name;
    END;
    When i execute the procedure GetEmployees i got this error :
    SQL> execute GetEmployees;
    BEGIN GetEmployees; END;
    ERROR at line 1:
    ORA-06550: line 1, column 7:
    PLS-00306: wrong number or types of arguments in call to 'GETEMPLOYEES'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    Please Help me in debugging this error. Thanks in advance.

    As the poster above mentioned you cannot call "GetEmployees" without a parameter.
    Note that the procedure declaration has the following line
    RCT1 IN OUT GLOBALPKG.RCT1
    This means that whenever you want to call the procedure you must pass it a variable of type GLOBALPKG.RCT1
    However unless this is merely a homework or learning exercise (i.e. you are not porting the code of a production application) i would strongly recommend that you do not attempt to simply convert the code to PL/SQL.
    The reasoning behind this is that Oracle's architecture will be completely different to the source of the original code and if you attempt to simply port the code (especially using an automatic tool) you will almost certainly hit problems.
    For example the SQL Server's 2000 code may (should be) be written based on SQL Server's locking strategy. Oracle's locking strategy is completly different if you try to use the same techniques as you do in SQL Server the performance will suffer.
    Porting a code or a database schema from one platform to another involves a lot of analysis in order to take advantage of the features of the destination platform.
    As I said this may not be important to you depending on why you are attempting a port.
    Good Luck.

  • SQL Developer export forgot to check to include semicolons in DDL

    Hi,
    I used the SQL Developers Export-function (select tables and right click on them, then select export) to backup tables.
    However, I forgot to set the 'Abschlusszeichen' (sorry for the german). That apparently means my create table statements are not finished by an ';', and they sinmply don't execute using the @script.sql method, or the sql developers import-function.
    One sql-file is 2 GB in size, so I currently have no idea how to edit it and add the semicolons manually. Is there any hope to rescue the data?
    I'm running sql developer 3.2.20.09, oracle Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production as well as Windows 8.1
    For clarification, this is how the create table part looks:
    --  Datei erstellt -Montag-September-30-2013  
    --  DDL for Table ZZ_BEN_0
      CREATE TABLE "PIERUSCHM"."ZZ_BEN_0"
       (    "BENUTZER_ID" NVARCHAR2(30),
        "NAME" NVARCHAR2(30),
        "GUELT_VON" NVARCHAR2(30),
        "GUELT_BIS" NVARCHAR2(30),
        "IST_KORREKTUR" NVARCHAR2(30),
        "IST_HALBTAGSKRAFT" NVARCHAR2(30),
        "LADE_DAT" DATE
    --  DDL for Table ZZ_BEN_1
      CREATE TABLE "PIERUSCHM"."ZZ_BEN_1"
       (    "BENUTZER_ID" NVARCHAR2(30),
        "NAME" NVARCHAR2(30),
        "GUELT_VON" NVARCHAR2(30),
        "GUELT_BIS" NVARCHAR2(30),
        "IST_KORREKTUR" NVARCHAR2(30),
        "IST_HALBTAGSKRAFT" NVARCHAR2(30),
        "LADE_DAT" DATE
    --  DDL for Table ZZ_BEN_10

    Also i'd like to add that the file begins with table definitions but then contains the actual (and randomly generated) data as well.
    You still need to have the file regenerated or you should expect to have problems with ANY method you use to try to automatically 'fix' the problem.
    1. No experienced developer that I have worked with would EVER try to execute such a monolithic script because there is virtually NO chance that a 2 GB script will EVER run successfully without an error of some sort. Objects have to be created in the proper order when dependencies exist between them. For example, you can't create an index if the table hasn't been created yet. There can even be circular references that will prevent all objects from being VALID even if they are created.
    2. There is virtually NO chance that ANY method you use will put terminators in EXACTLY the right place without causing a problem of some sort.
    3. When there is an error the script may continue to try to executed and that usually causes further errors. It also creates garbage objects that are not valid but will keep the script from working correctly the next time since the objects will already exist.
    You need to create a SET of scripts that are of manageable size so that you can control the process of executing them in the proper order.
    If you don't take the time to do that, up front, you are going to wasted a tremendous amount of time when the script fails trying to cut and paste the pieces you need out of that 'master' script.
    There are NO SHORTCUTS: take the time to do it right the first time.

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

  • Sql 2000 Connection Problems

    I am trying to install Sql Server 2000 at the moment but when i try to connect to local Windows NT server i get this messege http://img293.imageshack.us/img293/3263/connection8rq.jpg and if i go to properties of the server i get http://img369.imageshack.us/img369/1335/properties9dd.jpg. I believe it is trying to log in using my Windows Authications.
    Thanks for any help.
    James

    As per the error message it seems like the SQL 2000 Services has been stopped running due to login issue. You need to start up the service using a valide login.http://technet.microsoft.com/en-us/library/aa176564(v=sql.80).aspx
    Here we have the various ways to start up the services
    http://technet.microsoft.com/en-us/library/aa213795(v=sql.80).aspx
    Also please make sure that MSDE is installed properly.
    http://technet.microsoft.com/en-us/library/aa175272(v=sql.80).aspx
    Regards, RSingh

Maybe you are looking for