Before I get my hands dirty
I regularly backup the fme_job_history table for analysis. When I upgrade FME Server I'd like the job_id to remain consecutive instead of restarting from 1.
Is there a way to set the starting job_id after a re-install?
In SQL Server fme_job_history.job_id is not an identity column and I cannot see any hint in sqlserver_createDB.sql
The job_id attribute in fme_job_history comes from the table fme_jobs, which is an identity column.
From <FMEServer>\Server\database\sqlserver\sqlserver_createDB.sql:
CREATE TABLE fme_jobs (
job_id INTEGER NOT NULL IDENTITY PRIMARY KEY,
...The job id of fme_job_history probably comes from the fme_jobs table (and I guess the job row is moved from the fme_jobs to fme_job_history after completion).
If your database is postgres, maybe modifying the sequence fme_jobs_job_id_seq Current Value to what you want should do the trick.
On SQL Server, you should be able reseed the identity column as described here.
On Oracle, simplest way is to drop and recreate the fme_jobs_seq sequence with the correct value.
The job id of fme_job_history probably comes from the fme_jobs table (and I guess the job row is moved from the fme_jobs to fme_job_history after completion).
If your database is postgres, maybe modifying the sequence fme_jobs_job_id_seq Current Value to what you want should do the trick.
On SQL Server, you should be able reseed the identity column as described here.
On Oracle, simplest way is to drop and recreate the fme_jobs_seq sequence with the correct value.
The job_id attribute in fme_job_history comes from the table fme_jobs, which is an identity column.
From <FMEServer>\Server\database\sqlserver\sqlserver_createDB.sql:
CREATE TABLE fme_jobs (
job_id INTEGER NOT NULL IDENTITY PRIMARY KEY,
...
CREATE TABLE fme_jobs (
job_id INTEGER NOT NULL IDENTITY (65487,1) PRIMARY KEY,
...Might be wort for a knowledge base article with the other databases, too...
CREATE TABLE fme_jobs (
job_id INTEGER NOT NULL IDENTITY (65487,1) PRIMARY KEY,
...Might be wort for a knowledge base article with the other databases, too...