Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsExtension Verif...Extension Verif...SQL errorsSQL errors
Previous
 
Next
New Post
9/19/2016 9:47 AM
 

I get 2 types of SQL errors in the EVS:

1. error when creating a table with a generated sql script containing the with statement.
Incorrect syntax near 'tablename'. Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.

The with command is as follows: WITH (STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY].

2. Incorrect syntax near 'tablename' with no additional info

Module is tested for version 7.4.0 and up but when i install the module on 7.4.2 i don't get any error messages.

Could you extend the EVS to show more detailed SQL information? and why is the with command not accepted. If i place a semicolon (;) before the with statement the EVS validation doesn't give the first error but installing it on 7.4.2. failes because of it.

 
New Post
9/19/2016 10:17 AM
 
The first one is a false positive, not properly implemented check for CTE (which indeed have this requirement).
I am not sure about the second one, most likely it is the same issue. Make sure your script works on SQL Server 2012.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/19/2016 10:50 AM
 

Thanks for the fast reply.

The script works perfectly with SQL server 2012. I have taken another older module i created and is for DNN 7.1.1 and up. This gives the same error in EVS: Incorrect syntax near 'tablename'. But nothing more. When i install it on a clean dnn 7.4.0 installation it installs without any errors or warnings. The database is SQL server 2012 (version 11.0.5343).

Could this be a false positive in EVS as well? Or are you posible errors on Azure which are shown as errors by the EVS?

 
New Post
9/19/2016 11:29 AM
 
With latest version of Azure SQL, it has very little differences in SQL language towards SQL server, i.e. it is most likely a false positive as well.
Are you using any less common constructs in your scripts?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/20/2016 3:46 AM
 

No just simple table creates and CRUD stored procedures.

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsExtension Verif...Extension Verif...SQL errorsSQL errors


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out