Re: PeopleTools vs. std. Oracle

• Does PeopleSoft try to be platform independent? Yes.

Data Mover is still considered a PeopleTool. You access Data Mover outside of the Application Designer because you need to use Data Mover to create your installation databases before you ever have access to the other PeopleTools. PeopleSoft considers Data Mover a "universal" query tool. The script syntax you use in Data Mover is platform independent - even the PSCOPY command for Oracle has been removed from Data Mover at release 7.5. In previous releases, you could run some of your DB-specific ALTER and other SQL scripts in Data Mover. This has changed and explains why you started seeing at release 7 the warning in your SQL scripts that the script should be run in your RDBMS query tool.

• Can PeopleSoft perform all the processing it needs without caring what database you use? No.

PeopleSoft does care what platform you are using. This explains the warning to run SQL scripts using your RDBMS platform tool. SQL scripts should be run in your RDBMS tool; DMS scripts should be run in Data Mover. There is some functionality that is specific to your platform and the SQL script you generate in the Application Designer takes this into account.

An example of PeopleSoft creating platform dependent SQL scripts at release 7.5: you can no longer choose what type of SQL Alter you perform during a build. PeopleSoft now makes the choice for you - -- Alter In Place: SQLBASE, INFORMIX, Oracle (if your Oracle table does not have an image or long character field) -- Alter by Table Recreation: DB2 version 4.1 -- Alter by Table Rename: DB2 verion 5.1, DB2/400, DB2/Unix, Sybase, Microsoft SQL Server, Oracle (if your Oracle table has an image or long character field)

• Do I have to store Data Definition Language (DDL)information in PeopleSoft or do it with my database tool set? It's up to you. If you have the DDL in PeopleSoft, when you create/recreate tables, indexes, etc., this information will be in your SQL scripts. You may not have to tweak the scripts and this will make your upgrades easier as well. If you document your DDL changes and maintain copies of the scripts, you can feel free to work outside of the PeopleTools.

You may find using the PeopleSoft tools slower at first - until you become familiar with them, but they are worth considering. Try managing (create table, indexes, alter, views) a test table/view through PeopleTools and then do the same with your tool set. This may be the best way to see what meets your needs.

Jerome

As was mentioned earlier, if you update the Article <6s1nag$u2m$1_at_nnrp1.dejanews.com>,   jtesta_at_my-dejanews.com wrote:
> At best, the statement is a bunch of garbage, version 7 of peopletools, when
> doing alter commands, the script that gets generated says right at the top,
>
> --
> -- WARNING:
> --
> -- This script should not be run in Data Mover. It may contain platform
> -- specific syntax that Data Mover is unable to comprehend. Please use the
> -- SQL query tool included with your database engine to process this script.
> --
>
> This tells me right at the beginning, that not all of the changes that need to
> be made to a db must be done using PeopleTools. Anyone else's thoughts???
>
> joe
> http://www.oracle-dba.com

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum Received on Sat Aug 29 1998 - 18:13:41 CDT