Olympus configuration questions/problems

Chris_Knoll · July 13, 2015, 7:26pm

Sure, if those tables are not being used otherwise.

Edit:
He should also drop the table: dbo.schema_version. This is the flyway table that keeps track of which tables have been deployed. The reason why he should drop this is that the flyway DDL for MSSQL tests to see if the table already exists, and if so, considers it done. Example is here:

github.com

OHDSI/WebAPI/blob/master/src/main/resources/db/migration/sqlserver/V1.0.0.3__cohort_definition_persistence.sql

CREATE TABLE [${ohdsiSchema}].[cohort_definition](
	[id] [int] NOT NULL identity(1,1),
	[name] [varchar](255) NOT NULL,
	[description] [varchar](1000) NULL,
	[expression_type] [varchar](50) NULL,
	[created_by] [varchar](255) NULL,
	[created_date] [datetime] NULL,
	[modified_by] [varchar](255) NULL,
	[modified_date] [datetime] NULL,
	CONSTRAINT [PK_cohort_definition] PRIMARY KEY (id) 
) ON [PRIMARY]

CREATE TABLE [${ohdsiSchema}].[cohort_definition_details](
	[id] [int],
	[expression] [varchar](max) NOT NULL,
	CONSTRAINT PK_cohort_definition_details PRIMARY KEY (id),
	CONSTRAINT FK_cohort_definition_details_cohort_definition 
		FOREIGN KEY (id)
		REFERENCES ${ohdsiSchema}.cohort_definition(id)
) ON [PRIMARY];

So, if you don’t delete the dbo.schema_version, then it will try to continue where it failed last time, which is after the cohort_definition creation (which was skipped because it detected the table already existed), but the table that was there is the wrong table definition (it came from the CDM Schema). So, here’s what he needs to do:

DROP TABLE dbo.schema_version;
DROP TABLE dbo.cohort;
DROP TABLE dbo.chort_definition;

Then, next time he runs Olympus, it will run all the flyway migration scripts from step 0, and that will create the correct tables, and set up the proper database relationships.

-Chris