Orchard and SQL Server 2014

Topics: General
Jun 27, 2014 at 10:05 AM
Is Orchard compatible with new SQL Server 2014?
Did the authors test it against new sql server version?
Mar 14 at 9:00 AM
Hi Team,

Can you please reply for this query, because, we are using Orchard 1.9.2 and SQL 2014. After deployment in dev server, and while querying search, or Odata queries etc, its giving SQL Timeout error.

"System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out"
Mar 14 at 9:02 AM
Please let us know if any known performance / SQL Connectivity issues with Orchard 1.9.2 and SQL 2014 Enterprise version.
It would be great help for us to proceed. Thanks a lot.
Developer
Mar 14 at 9:40 AM
Orchard runs fine with SQL Server 2014. Unfortunately I don't know why you're getting the timeout error. Can you open a ticket on GitHub with repro steps?
Mar 14 at 10:16 AM
Thanks for your reply.

We have SQL 2012 and 2014(recently installed) in our dev server.

We have hosted our Orchard 1.9.2 site in the same dev server.

We are using Orchard.OData module ( from gallery) to meet our requirement, as we are using orchard as a service.

if we hit OData query from our front-end app(AngularSPA) via service calls, its throwing the Timeout error as said above.

Even if its a simple query (https://domain/odata/EntityName?$filter='value' Thank you.
Mar 14 at 11:40 AM
Developer
Mar 14 at 5:02 PM
That's probably an issue with the module - since Orchard.OData is a 3rd party extension, it isn't specifically tested for the Orchard releases, so please try to contact the author of the module. If the author of the module does not respond, we can probably help too if you provide more information.
Developer
Mar 14 at 5:06 PM
Alternatively, it's possible that you have a lot of content items and query on something that is only stored in infoset, so all the content items of the relevant type will be fetched. Did you try to specify the connection time out period in the connection string?