Having the same exact problem as well. However, I'm starting to think the solution is to stop using SQL CE if at all possible. CE won't be compatible with Windows 10.
I get that you feel frustrated about this nice package not working with the CE SQL database. But keep in mind that it's a time consuming task to develop and maintain packages. And do keep in mind that it's something people are doing voulentarily because they create something awesome that they want others to benefit from - But sometimes one can easily forget how many databases it needs to be compatible with, which can make it more complex to make sure it works on every single database. CE SQL for instance uses a subset of the SQL that MSSQL supports, which I suspect is the reason that you guys are experiencing these issues. According to the release notes on the package page it seems that CE SQL should be supported since version 1.3 - However this package has existed for some years and a lot have happened since then so things might have changed in the CE SQL database or maybe it's something in Umbraco that has changed meaning that the package is no longer working with CE SQL. Or perhaps it's because an old version of CE SQL is being used - There can be a lot of uncovered scenarios that the package author would have no chance of knowing about.
I say this just so that you keep in mind that the creator or the package has probably only had the best intentions but is probably struggling with keeping up supporting all the released packages he has made. I'm sure a pull request to the source code with a fix for this issue would be very much appreciated - However I'm also aware that not everyone is capable of doing that - I myself would not know where and what to look for in this case. But perhaps you have the skills to do it? Or maybe you know someone else who has the skills and can go and fix it for instance? - That would help not only you but others as well and especially the creator of the package too.
Like I said I get that you're frustrated but keep in mind how comments can affect the motivation and willingness for people to keep contributing and do their best - that's all :)
I just thought I´ll chip in that one option for CB, Shola, Arjan and Wesley could be to convert their CE database to a MsSql server database. Thats what i´ve done on a few occasions when a package i really wanted did´nt support CE.
Yes migrating from CE SQL to MSSQL will of course solve the issue. But as you mention it might not be the solution for everyone since it can be an additional cost to have a MSSQL database, which not everyone / project / company for some reason can afford.
Webmatrix also has a nice "migrate" feature - So if one chooses the "Database" tab then in the ribbon that appears there is a "Migrate" ribbon in the top right corner, which will become green when one has chosen the database to migrate.
Since MS SQL Express is free, hopefully affordability is not an issue. Furthermore, not only is CE incompatible with Windows 10, but also CE is in deprecation mode itself. I've heard from Umbraco HQ that they're working to eventually move away from CE for these reasons. Perhaps one of their alternatives is LocalDB, but my advice now is to permanently migrate off of CE if at all possible, to avoid future issues well outside of this plugin.
Ah yes! Totally forgot about the Express edition - you're absolutely right :)
Ooops, hit the wrong button when wanting to respons - answering from my phone and my fingers are simply too big so by mistake I marked this post as solvef, which is not the case. My bad #h5is
SQL CE support
Hi Matt,
Thanks for updating this great package!
When I'm using the package with a SQL CE database I reveice the following postsave error:
Wesley
Having the same problem. Would be great if SQL CE is supported too.
Having the same exact problem as well. However, I'm starting to think the solution is to stop using SQL CE if at all possible. CE won't be compatible with Windows 10.
Add my vote as well to this issue. How can we make packages that don't support native database types that the CMS is compatible with!?
Awesome package, but won't work on any of our sites...
Hi CB
I get that you feel frustrated about this nice package not working with the CE SQL database. But keep in mind that it's a time consuming task to develop and maintain packages. And do keep in mind that it's something people are doing voulentarily because they create something awesome that they want others to benefit from - But sometimes one can easily forget how many databases it needs to be compatible with, which can make it more complex to make sure it works on every single database. CE SQL for instance uses a subset of the SQL that MSSQL supports, which I suspect is the reason that you guys are experiencing these issues. According to the release notes on the package page it seems that CE SQL should be supported since version 1.3 - However this package has existed for some years and a lot have happened since then so things might have changed in the CE SQL database or maybe it's something in Umbraco that has changed meaning that the package is no longer working with CE SQL. Or perhaps it's because an old version of CE SQL is being used - There can be a lot of uncovered scenarios that the package author would have no chance of knowing about.
I say this just so that you keep in mind that the creator or the package has probably only had the best intentions but is probably struggling with keeping up supporting all the released packages he has made. I'm sure a pull request to the source code with a fix for this issue would be very much appreciated - However I'm also aware that not everyone is capable of doing that - I myself would not know where and what to look for in this case. But perhaps you have the skills to do it? Or maybe you know someone else who has the skills and can go and fix it for instance? - That would help not only you but others as well and especially the creator of the package too.
Like I said I get that you're frustrated but keep in mind how comments can affect the motivation and willingness for people to keep contributing and do their best - that's all :)
Ok, that being said I'm wondering what version of Umbraco that you guys are using? And is it failing locally or is it on some hosted environments that it's failing? I recall seeing this error message before in another context and perhaps the advice Sebastiaan is giving here could solve things in this scenario? https://our.umbraco.org/forum/umbraco-7/using-umbraco-7/52871-Umbraco-7-not-possible-in-production-with-sql-ce#comment-183933
Cheers, Jan
Very nice read Jan, as always! :)
I just thought I´ll chip in that one option for CB, Shola, Arjan and Wesley could be to convert their CE database to a MsSql server database. Thats what i´ve done on a few occasions when a package i really wanted did´nt support CE.
Its might sound scary and timeconsuming, but it´s acctually not very tricky, takes less than an hour and i usally follow this great tutorial http://www.geektantra.com/2012/10/umbraco-deployment-exporting-ms-sql-ce-database-to-ms-sql-server-express/ and have never had any problems with it.
I understand that this might not be an answer to everyone, but it might be an option for some.
Best of luck everyone!!
Why thank you Dennis :) - Likewise!
Yes migrating from CE SQL to MSSQL will of course solve the issue. But as you mention it might not be the solution for everyone since it can be an additional cost to have a MSSQL database, which not everyone / project / company for some reason can afford.
Webmatrix also has a nice "migrate" feature - So if one chooses the "Database" tab then in the ribbon that appears there is a "Migrate" ribbon in the top right corner, which will become green when one has chosen the database to migrate.
Just my 2 cents on the migrate option :)
/Jan
Since MS SQL Express is free, hopefully affordability is not an issue. Furthermore, not only is CE incompatible with Windows 10, but also CE is in deprecation mode itself. I've heard from Umbraco HQ that they're working to eventually move away from CE for these reasons. Perhaps one of their alternatives is LocalDB, but my advice now is to permanently migrate off of CE if at all possible, to avoid future issues well outside of this plugin.
Ah yes! Totally forgot about the Express edition - you're absolutely right :)
Ooops, hit the wrong button when wanting to respons - answering from my phone and my fingers are simply too big so by mistake I marked this post as solvef, which is not the case. My bad #h5is
is working on a reply...