Toad World® Forums

Editor script execution fails on Toad-ss-5.5.0.683 [1 Attachment]


#1

[ Attachment(s) from Hank_Freeman included below]

—Just tried to run this statement on Toad-SS-Beta, but could not …
Worked fine on SSMS 2008 R2 …

select top 50
contactSerialNumber, enc.VisitProviderKey
from
clinical.FactEncounter enc
inner join common.DimDate dt on dt.DateKey = enc.EncounterDateKey
inner join clinical.DimEncounterAttributes atr on
atr.EncounterAttributesKey = enc.EncounterAttributesKey
inner join clinical.DimProvider prv on prv.ProviderKey =
enc.VisitProviderKey
inner join clinical.DimDepartment dep on dep.DepartmentKey =
enc.DepartmentKey
inner join clinical.DimContactSerialNumber csn on
csn.ContactSerialNumberKey = enc.ContactSerialNumberKey
where
CalendarYear = 2011
and IsFaceEncounter = ‘Yes’
and prv.RegionalProviderID = ‘’


#2

Hank,

By saying this you mean that you can’t it execute it at all or only once?
The script below is quite simple. It seems to me that the issue is not in the
script, but in some previous actions (change connection, lost connection,
reconnect etc.) so Editor use wrong meta data.

regards,

Alexander Maximov


#3

Alex, I can go along with that, but regardless of the fact that the select
statement had been edited several times does not excuse the fact that the editor
failed. The application needs to be totally resilient in it’s ability to
allow the user to edit a file without application failure. Like all programmers
I can make good SQL Syntax that works pretty much all the time, but I also need
an editor that will allow me to make syntax errors, fix then and then run…
The reality is that the editor simply cannot do these basic functions makes it
UNREADY for any consideration of release.

This is the sermon I am preaching and have been preaching for a while,
regardless of any other or new features that are present in the editor. I have
been assured in the past that R&D understands the importance of a stable usable
product.

J

Hank Freeman

Senior SQL Server DBA/Data & Systems Architect

hfreeman@msn.com

678-414-0090 my cell Primary
image001.gif


#4

Alex, I can go along with that, but regardless of the fact that the select
statement had been edited several times does not excuse the fact that the editor
failed. The application needs to be totally resilient in it’s ability to
allow the user to edit a file without application failure. Like all programmers
I can make good SQL Syntax that works pretty much all the time, but I also need
an editor that will allow me to make syntax errors, fix then and then run…
The reality is that the editor simply cannot do these basic functions makes it
UNREADY for any consideration of release.

This is the sermon I am preaching and have been preaching for a while,
regardless of any other or new features that are present in the editor. I have
been assured in the past that R&D understands the importance of a stable usable
product.

J

Hank Freeman

Senior SQL Server DBA/Data & Systems Architect

hfreeman@msn.com

678-414-0090 my cell Primary
image002.jpeg