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...When reporting SQL errors, show offending SQL line number etcWhen reporting SQL errors, show offending SQL line number etc
Previous
 
Next
New Post
12/13/2012 12:36 PM
 

Title speaks for it self. Would be good to show the actual offending line number, and possibly even the actual line. Otherwisel, it could be quite some work finding the errors in your file


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
12/14/2012 8:46 PM
 
I'll second that! EVS found a number of SQL Azure incompatibilities - mostly ( nolock ) table hints and Not For Replication on foreign key constraints - on several old scripts. As they were long scripts it took quite a while to locate the offending lines without knowing exactly what to search for. I then had to run the corrected package through EVS a second time to be sure that I had not missed anything.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
12/20/2012 6:37 PM
 
Hey Guys,

Thanks for the feedback!

I've made an update to the site that I hope you will find helpful. Now if your extension has SQL scripts, the results of the SQL Azure migration wizard will be zipped up and available via a download link from the results page. These are the original scripts provided with the corrections already made by the migration wizard, and comment near the modified area. With these files, you should be able to use a tool like beyond compare to quickly identify the changes made to make the files SQL Azure compatible. As always please test these new scripts as the changes were made by an automated tool and could adversely affect the function of the extension.

If you take a look at this result page ( http://evs.dotnetnuke.com/results.htm... ), you can see a new link at the bottom of the right hand side that will allow you to download the results.

Please let me know if you have any questions or comments.

Cheers,

Nathan Rover
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsExtension Verif...Extension Verif...When reporting SQL errors, show offending SQL line number etcWhen reporting SQL errors, show offending SQL line number etc


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