Timo,

I answered this in another thread (that I can't find anymore?) already. First of all: SQL Server 2016 and SQL Server 2017 have already passed the mainstream update phase, so you don't get any security updates anymore (except when you pay a lot of money for extended upgrades). Therefore, using SQL Server 2019 or 2022 is the recommended solution.

The problem can be found in the file 09.11.01.SqlDataProvider in the installation package for Dnn.PersonaBar.Extensions, lines 25 and 53. This syntax ("DROP PROCEDURE IF EXISTS"...) was introduced with SQL Server 2016, it was one of the few things I always liked in the Oracle PL/SQL "dialect". What a pity, they did not introduce this consequently. Another example for this is "CREATE OR ALTER PROCEDURE..." - these commands work with Stored Procedures and Functions, at least in SQL Server 2019, but not with Views. :-(

The solution is either upgrade your SQL Server (better way!) or replace the lines with

IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'{databaseOwner}{objectQualifier}UpdateIPFilter') AND type in (N'P', N'PC'))
      DROP PROCEDURE {databaseOwner}{objectQualifier}UpdateIPFilter
GO

and

IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'{databaseOwner}{objectQualifier}AddIPFilter') AND type in (N'P', N'PC'))
      DROP PROCEDURE {databaseOwner}{objectQualifier}AddIPFilter
GO

before you install DNN.

Maybe someone should change the DNN Platform Requirements -- DNN Docs (dnncommunity.org) and eliminate at least SQL Server 2012 and SQL Server 2014, better also 2016 and 2017.

Happy DNNing!
Michael

Oh, I thought the most current supported SQL Server version was already 2014 and higher.  🤔 

Posted By Will Strohl on 2/27/2023 6:13 PM

Oh, I thought the most current supported SQL Server version was already 2014 and higher.  🤔 

Well - that's not in the docs...

Anyway: There is a statement in the setup/upgrade SQL scripts that requires SQL Server 2016 or higher, therefore SQL Servers 2012 and SQL Server 2014 should be excluded from the minimum requirements, at least for DNN version 9.11.1. We should discuss if SQL Servers are supported that are already past the MS Mainstream Support (for security reasons I would say: No), in this case SQL Server 2016 and SQL Server 2017.

The problem is obviously that someone generated that part of the script with the script creation tool in SSMS using a newer SQL Server, and was not aware about the consequences in older SQL Server versions.

Happy DNNing!
Michael