: the SPDELETE stored procedures do not remove a project or a task completely from the Database. The Stored Procedure moves a project from the PROJECTS Table to the ARCHIVEPROJECTS table and/or a task from the TASKS to the ARCHIVETASKS table, similar to what is done when a project is archived by the Garbage Collector.
However, please be careful: deleting a project or a task from a Database is an irreversible action. A project cannot be made active and visible again after running the stored procedures mentioned below. Make sure you enter the correct data and you are really sure that you want to perform a deletion.
First, you need to determine which type of Database is running on the affected SDL WorldServer environment: Oracle
1- To remove a Project
, refer to the Project ID
the Project Group ID) displayed in the project page.
If you are working with an Oracle Database, use this stored procedure
exec spDeleteProject (projectID)
and make sure you (or the Database manager) does a commit; Here is an example:
exec spDeleteProject (224356)
If you work with an SQL Database, the query to delete the project would be:
exec spDeleteProject projectID
2- To remove a Task from the Database, first find the Task Id
. This might be mentioned in an error message, or you can find that by hoovering with your mouse cursor on the Task number as explained in this screenshot:
1- To delete a Task in an Oracle
hosted environment, access the Database and then run this query
exec spDeleteTask (taskID)
with the actual taskID, for instance
exec spDeleteTask (473914)
On SQL Servers
you can execute the Stored Procedure spDeleteTask
and pass Task ID as parameter value. For instance:
exec spdeletetask 473914
: these stored procedure do not remove the project or task completely from the Database. It moves them from the PROJECTS Table to the ARCHIVEPROJECTS table and/or from the TASKS to the ARCHIVETASKS table, similar to what is done when a project is archived by the Garbage Collector.