Network Management
"Error while executing script- Database and server triggers on DDL statements CREATE, ALTER and DROP are not supported with memory optimized tables." in Configuration Wizard when deploying the SolarWinds Platform
Workaround to "Error while executing script- Database and server triggers on DDL statements CREATE, ALTER and DROP are not supported with memory optimized tables."
First published date
Last published date
Overview
When setting up a new SolarWinds instance and creating the 3 databases, you may encounter the error "Error while executing script- Database and server triggers on DDL statements CREATE, ALTER and DROP are not supported with memory optimized tables" when running the configuration wizard.
The resource below is often used to resolve this issue; however, it can't be applied in this case as the configuration wizard failed to even create the database:
This typically occurs due to DDL server-level policies on the SQL server, and it's recommended to disable them. However, if you are unable to disable the policies, as a potential workaround, you can migrate the SolarWinds database from a SQL server that doesn't have these policies to get around them.
Product section
Cause
The configuration wizard is unable to create the database due to below error
The below KB cannot be used as the database has not been fully created yet. The configuration wizard marks that database as incomplete because it failed last time.
By running the script below, it was identified that server-level triggers were causing DDL triggers to be automatically applied, which in turn caused the configuration wizard to fail.
-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.
SELECT name, is_disabled
FROM sys.server_triggers;Resolution
The resolution would be to either disable any DDL triggers so that the SQL server doesn't apply them on table creation. Alternatively, in a new environment, as a potential workaround, create the SolarWinds databases using a SQL server that doesn't have any policies like this, migrate the tables, and run the configuration wizard.