We have a client that needs to use MS SQL for their database.
We started with 11.7.2 and had all sorts of client session crashes. PSC advised to upgrade to 11.7.3. This solved the initial crashes only to create different ones... I have calls logged with tech support for this.
While waiting on an official resolution I wanted to throw this out there, see if anyone else is using OE 11.7 with MS SQL and if so which service pack level of OE and what has been the experience to date.
We have clients using OE 11.5 with MS SQL without any known issues...
Funny enough it is exactly that FOR EACH customer, FIRST order OF customer that gives us grief in 11.7.3.
That type of query crashes the client session for us in 11.7.3... The same code compiled with 11.7.2 works fine with 11.7.3 dataserver and 11.72 or 11.7.3 client. I raised a ticked with support for it (00448655).
Was wondering what other gremlins await us there...
I think it's the 11.7.3 compiler that has some issues. We get the crash when we compile the code with 11.7.3 and run with 11.7.3 client & dataserver. The same code compiled with 11.7.2 runs fine with 11.7.3 client/dataserver or 11.7.2 client/dataserver. So the 11.7.3 compiler is the difference... I've updated tech support.
Changing the code is not really a workaround. It's not one query that has the problem, it's the basic FOR EACH, FIRST join construct that has an issue. We can't change *all* such queries... We would need a client startup parameter to turn that tuning off everywhere.
Found the -nojoinbysqldb startup parameter, but I suppose that will also apply to FOR EACH, EACH queries which actually work fine.
So we eliminate the crash, but take on a performance hit...
Thank you for posting this problem, we are affected too. Every Single-Shot Query (FOR EACH, FIRST) is generating an error.
Fehler (Press HELP to view stack trace)
37000: [Microsoft][ODBC SQL Server Driver][SQL Server]Wrong syntax near '-'.
You are getting an error message? You are lucky, we are getting a session crash :)
Try the log options suggested by Mukesh above and see what the logs say, maybe that will provide some hints.
Out of curiosity what OS are you using? At the moment we get the crash on win10 and win7, no crash on win server 2012. Also would you be able to check the version of vcruntime140.dll used by your prowin client?
Happy to report that is the only issue we currently have, everything else seems to work fine. The -nojoinbysqldb startup parameter got rid of the crash...
You are right, the user has an hypen, but I don't think, that this is the problem, because it is working as soon as
-nojoinbysqldb is used. I opened a support ticket with Technical Support.
System32 vcruntime140.dll - Version: 14.0.24210.0 (9June 2016)
SysWOW64 vcruntime140.dll - Version: 14.0.24212.0 (13July 2016)
Client System is Windows 10 x64.
Unfortunately, -nojoinbysqldb is only working at compile time and it have a huge performance hit.
Thank you for your help. The problem is related to a database name with a hyphen. After changing the database name to a name without a hyphen, the problem went away. A test with some single-shot queries worked without any problems.