View Incident Report

Serious

Reported By: James Relyea
Reported On: 1/25/2009
For: Version 2.02 Build 7

# 2911 Visual Studio Query Designer Using Improper SQL Syntax for JOINs

When using MS VS2008, and creating a New Query, Select statements are being rewritten with ElevateDB. I compared the behavior against VistaDB, and it does not happen.

The following Select statement is what I pasted in to VS's QBE, and what it was changed to.

My problem is with performance. The latter will hang the ElevateDB Unicode server with my CPUs pegged @ 100% for several minutes before it errors out. The query I pasted in using Inner Joins returns results in <1 second.

SELECT        tCorps.varFullName, tPhNums.idPhNumId
FROM tCorps inner join tPhNums on tCorps.idCorpId=tPhNums.idCorpId
inner join tPhNums_Sec on tPhNums.idPhNumId=tPhNums_Sec.idPhNumId
inner join tsecGrp_tUsers_XRef on 
tPhNums_Sec.idSecGrpid=tSecGrp_tUsers_XRef.idSecGrpId
where tCorps.varFullName like 'c%'

Rewritten in VS to become:

SELECT        tCorps.varFullName, tPhNums.idPhNumId
FROM            tCorps, tPhNums, tPhNums_Sec, tSecGrp_tUsers_XRef
WHERE        tCorps.idCorpID = tPhNums.idCorpId AND tPhNums.idPhNumId = 
tPhNums_Sec.idPhNumId AND tPhNums_Sec.idSecGrpId = 
tSecGrp_tUsers_XRef.idSecGrpId AND (tCorps.varFullName LIKE 'c%')

Comments

The problem was in the DDEX integration in the ElevateDB .Net Data Provider that didn't convey the proper information to the Visual Studio Query Designer so that it could use the proper syntax.

Resolution

Fixed Problem on 2/10/2009 in version 2.02 build 8

Products Affected

ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap