I can confirm this issue, when saving to the Page table, I get this error too. Just with the number 44446 instead.

I am running SQLExpress 2012

Seems it is discontinued functionality that causes a trigger to fail.

http://technet.microsoft.com/en-us/library/ms144262.aspx: RAISERROR in the format RAISERROR integer 'string' is discontinued.

So that is noted. Thanks for the heads-up.

Regards /Snedker

Do you guys have any plans supporting 2012 in the near future?

In that case approximately when and will it also be fixed on dw7 versions?

Regards / Magnus

Hi Magnus,

>> Seems it is discontinued functionality that causes a trigger to fail.

Yeah, that's indeed the case. Deleting all the triggers from the database seems to do the trick. We did some testing on this in the US and so far everything seems to work fine without the triggers....

Take a look here: http://www.sqlservercentral.com/Forums/Topic285605-5-1.aspx to find a quick way to delete all triggers from a database. Use at your own risk though. If this is for a production site, I would wait for an official 2012 compatible database.

Imar

I start to meet customers with SQL Server 2012 - had to tell them that it's not compatible yet.

Hi Kevin

It is in the Works, and we plan to have it out officially before Christmas.

I run locally only SQL-Server 2012 and IIS 8 - it Works with the change Imar mentions, both will have official support very soon - we just need to run a complete set of tests and create a database for SQL 2012 before going official.

//Nicolai

I get the error when trying to save a new paragraph in DW 8.2.1.0 running on SQL Server Express 2012 and IIS8.

Serverfejl i programmet '/'.

---

Incorrect syntax near '44446'.

[SqlException (0x80131904): Incorrect syntax near '44446'.]
   System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +388
   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) +688
   System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) +4403
   System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout) +2755286
   System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite) +527
   System.Data.SqlClient.SqlCommand.ExecuteNonQuery() +290
   Dynamicweb.Database.ExecuteNonQuery(String sql, Int32 commandTimeout, Boolean useTransaction, String database, IDbConnection connection) +1358
   Dynamicweb.Database.ExecuteNonQuery(String sql) +36
   Dynamicweb.Admin.ParagraphEdit.SaveParagraph() +2514
   Dynamicweb.Admin.ParagraphEdit.Page_Load(Object sender, EventArgs e) +3368
   System.Web.UI.Control.LoadRecursive() +71
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3178

Hi Paul,

Check my previous post in this tread. SQL Server 2012 is not supported yet. But if you want to continue, you need to delete all the triggers from the database first.

Cheers,

Imar

Hi Imar,

Yeah I read that, but Nicolai stated they had planned support for SQL Server 2012 before Christmas.
Any news on the subject as we have entered February 2013?

Regards
Paul

Hi Paul

Yes - it is being finished as we speak. But not released yet though. Cannot say anything precise on ETA since it has to pass testing first.

Saw testing reports this morning with only a couple of minor Things left, so it should be soon.

(BTW - running SQL-Server 2012 and IIS8 myself with no issues with the changes Imar has written above)

BR Nicolai

Has there been any development on this issue since February.

I too have a customer which is using SQL 2012 and they are experiencing the above mentioned problems.  

Regards

Frode

Hi Frode,

Yes, there has been some Development regarding SQL 2012 support. With the release of 8.2.2.3, you should be able to run DW on SQL 2012 without any issues. It's not officially announced though. We have, however, not made a new Default Empty Data yet. We will release a new Default Empty Data along with official support for SQL 2012 with the release of 8.2.3.0 in May.

- Jeppe

Hi Nicolai

I have experienced problems with the indexing process on IIS 8 otherwise SQL-server 2012 is working great

Best regards,

Anders

Hi Jeppe,

Should a new "Default Empty Data" still be released for sql 2012 databases?
Because from the downloads DefaultEmptyData8SQL.zip  it is dated from 07-06-2012.

 

Same here. Customer is running W2012 with SQL 2012. I will give them feedback that it's currently not supported.

However, I'm a bit puzzled by the suggestion to delete the database triggers. Aren't these triggers essential for the operation of DW?

Thank,

Ton

Hi,

Remi: yes, there will be a default empty database for SQL2012. I'll kick some legs for answers - I'm not aware of the status myself.

Ton: Not essential triggers. If you were to delete these triggers, you should be aware of the consequence, and make sure that you handle the effect. For instance re-writing them to match SQL2012. Deleting them was mentioned as a work-around.

Regards /Snedker

(Morten:) If I script the DefaultEmptyData database, there seems to be no trigger at all.
Am I right?
Could it be that this Trigger logic is moved to the code-behind ?

Regards,
    Jeroen Elias

Hi Jeroen,

No, that could not be. :-)

If you download the default database from our Developer site, you'll find 119 triggers. ;-)

I am not aware where you've obtained the database you are referring to...

Check with:

Regards /Snedker

I'm afraid you are right. Please discard my comments ;-(

But recently I upgraded one solution from DW7 to the latest 8.3.1.11
In that database, all triggers are gone.
I suspect during the upgrade from DW7 these triggers are removed by the update procedure.

Yes, some triggers are removed. They are from good old days making sure of cascading updates/deletes. That is handled by the database now, or by the code deleting things.

This change was part of the behavior change of making Dynamicweb 2012 compaible. We removed the problematic triggers in the update and the new application takes care of the cascades instead.

Nicolai

Our customer experiences the 44446 error on SQL2012. After that they configured SQL2012 to run in 2008 compatibility mode, however, the error remains. Is that to be expected?

Thanks

Hi Ton

Yes.

Run this piece of code against the database:

SELECT 'drop trigger ' + name , * FROM sys.objects WHERE type_desc = 'SQL_TRIGGER'

Make sure you run on 8.2+ - it will not require the triggers.

BR Nicolai

Hey Umar,

I get the same SQL error as mentioned above: 'incorrect syntax near 44446', however I am not able to find the database triggers - the folder in the database is empty. Any workaround on this?

/MikkelTO

Take a look under the Triggers node for each table; they might be there. Or run:

SELECT 'drop trigger ' + name , * FROM sys.objects WHERE type_desc = 'SQL_TRIGGER'

to get the code to delete the existing triggers.

Cheers,

Imar