System.Data.SqlClient.SqlException (0x80131904): Invalid column name 'True'. at System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String connectionString, String script) UPDATE dbo.[Tabs] SET IsSecure = True WHERE PortalID = 0

Again, please advise.

The above solutions from the Forum seems to work... Wanted to say thank you to all the DNN forum developers.
I also found the following to work well if you have direct access to the DB

UPDATE Tabs SET IsSecure = 1

The only catch is... which ever way you decided to force your entire DNN Site behind SSL, Make sure you disable SSL Required in IIS settings. Our findings In IIS as we found that forcing SSL as "Is Scure" on the DNN pages and iis's "SSL Required" in IIS will give you a page not found error. Removing the "SSL Required" from IIS seems to keep the two from conflicting... and all the pages successfully force to https without the need of SSL Required from IIS .... DNN seems to control that. This seems to resolve the issue in our case... may differ for others... but just something to watch for if you are having to use dnn 6.2.x.

Was curious if this is as complicated in DNN 7. x ? Is it more automated?

Again, thanks for the answers from the forum it seems to have helped me resolve this issue for now.

 Kind Regards,