Toad World® Forums

General feedback


#1

Dear all,

I have been using Toad SS Betas for my productive work, because I
really want this mostly great product to be improved. However, the
last beta (317) has been breaking down my working speed so
dramatically, I am sorry to say that I have to go back to 5.0. Please
don’t take it as an offence, but this has been the most buggy Beta
ever. Furthermore, the bugs I encounter in this beta are hardly
reproducible, which makes the software crash or make it unstable to a
point that I have to kill the process from the task manager. I regret
that I am not going to be able to give feedback about it till the next
Beta. I never mean to discourage you, since I believe you are doing
mostly a great job, but I just wanted to let you know the situation.

Regards
Ercan


#2

Ercan you have properly stated the status of the Beta !!

I too have work to get done and had to go back to 5.0.2 because of issues with
the Beta release that should have never occurred at the Beta level.

I have time for Beta work and will make time for it, but I have no time for Beta
testing where there are so many errors that should never have been part of a
Beta release.

I have tried to use the 317 beta, but I had to back-off my testing for I simply
could not rely on the software.

There have been so many voices on this last Beta release speaking up, that I
felt that it was time for those voices to be heard so I have been a silent
observer.

Bottom Line, we need a more competent Beta release for our time is our employers
time and we are getting paid by them not Quest.

Therefore, please do not release a Beta until you have thoroughly gone through
the software… We as BETA testers, should be acknowledging fixes and new
features as usable and of value.

The Beta software release should pass QA/QC testing first then be posted for
Quest Beta partners to evaluate !!!

WE HAVE NO TIME FOR HALF BAKED SOFTWARE BETA RELEASES .

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678-414-0090 my cell Primary
image002.jpeg


#3

Ercan you have properly stated the status of the Beta !!

I too have work to get done and had to go back to 5.0.2 because of issues with
the Beta release that should have never occurred at the Beta level.

I have time for Beta work and will make time for it, but I have no time for Beta
testing where there are so many errors that should never have been part of a
Beta release.

I have tried to use the 317 beta, but I had to back-off my testing for I simply
could not rely on the software.

There have been so many voices on this last Beta release speaking up, that I
felt that it was time for those voices to be heard so I have been a silent
observer.

Bottom Line, we need a more competent Beta release for our time is our employers
time and we are getting paid by them not Quest.

Therefore, please do not release a Beta until you have thoroughly gone through
the software… We as BETA testers, should be acknowledging fixes and new
features as usable and of value.

The Beta software release should pass QA/QC testing first then be posted for
Quest Beta partners to evaluate !!!

WE HAVE NO TIME FOR HALF BAKED SOFTWARE BETA RELEASES .

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678-414-0090 my cell Primary
image001.gif


#4

Dear all,

I have been using Toad SS Betas for my productive work, because I
really want this mostly great product to be improved. However, the
last beta (317) has been breaking down my working speed so
dramatically, I am sorry to say that I have to go back to 5.0. Please
don’t take it as an offence, but this has been the most buggy Beta
ever. Furthermore, the bugs I encounter in this beta are hardly
reproducible, which makes the software crash or make it unstable to a
point that I have to kill the process from the task manager. I regret
that I am not going to be able to give feedback about it till the next
Beta. I never mean to discourage you, since I believe you are doing
mostly a great job, but I just wanted to let you know the situation.
[…]

I just considered to write similar letter, but focused on different points.
I do not feel who is the target of this product. Why?
Because as a sql [experienced] programmer I do not find [m]any advantages
against Enterprise Manager.
Imho tool is heading to become a data analyze tool [master / detail browser,
pivot and chart]

Programming tools looks fine, but only looks ;(

  • Query Builder - I have to exactly know structure to build query [finding
    lookup table is far below expectation]
  • It not allows to use nested tables and so on.
  • Editor - message window ‘catching’ focus after execution, a lot of strange
    exception
    Code Completion - work fines, but to simple scenario. When there are nested
    queries - if fails.
    Code Optimization - I have to adopt code to run CO. Result: I never found
    solution better then mine.
    Looking in alternative code - there is no chance beat score using such methods.
  • Browser - good collection of distributed information about objects, but:
  • look at Foreign Key information: there is referenced table and column… but
    what column is referring to this objects?
  • altering tables from Browser - I sent a mail about issues
  • Diagram - another set of issues. I cannot use it to design a new objects, I
    cannot send subset of tables to QB
  • Automation - it simply does not work.
  • Master Detail browser - tool not for programmers.

I made some proposals of new function and gain no feedback - ok, I accept it,
but why information about error
are treated the same manner?

sad…

Butter


#5

Motyl,

Couple of words about Automation. I just want to remind that what I’ve already
posted: The version of Automation that you see in the latest beta was under
development when beta 317 was posted. It was not supposed to be finished before
Toad for SQL Server 5.5 feature freeze and that is why it was decided that
ToadSS 5.5 will contain the previous version of Automation engine which in
particular doesn’t feature Activity input controls and shouldn’t therefore
have all those validation synchronization issues you reported. Just take a look
at Automation in the next beta and see if all/any problems will be there.

Thanks,

Igor.


#6

Witam!

Motyl,

Couple of words about Automation. I just want to remind that what I’ve
already posted: The version of Automation that you see in the latest beta was
under development when beta 317 was posted. It was not supposed to be finished
before Toad for SQL Server 5.5 feature freeze and that is why it was decided
that ToadSS 5.5 will contain the previous version of Automation engine which in
particular doesn’t feature Activity input controls and shouldn’t
therefore have all those validation synchronization issues you reported. Just
take a look at Automation in the next beta and see if all/any problems will be
there.

Igor,

you are right - you posted this info. I just mentioned about automation when I
passed through main [/top level]

features which are included in that beta.

What about other issues I mentioned?

Butter


#7

LOL

Witam indeed !!!

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary
image001.gif


#8

LOL

Witam indeed !!!

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary
image002.jpeg


#9

LOL
Witam indeed !!!

such template. I missed to correct it ;). It means ~greet.
I hope you don’t find this mail impolite. [maybe a little to inquiring].

Butter


#10

Motyl,

For about this question:

What about other issues I mentioned?

We are(will) definitely review all of your reported issues. Sorry for the delay
with responses, we didn’t miss them – just busy with our activities.

regards,

Alexander Maximov

Quest Software