Toad World® Forums

Couldn't open old schema context [1 Attachment]


#1

[Attachment(s) from Hackett, Eric included below]

I got this message the first time ( and every time since ) I opened Toad 5.0.0.291
I am unable to view tables in the database explorer, but the views tab does get populated.

I am finding it very frustrating that new builds seem to have new problems without having addressed any of the existing issues. It feels like Toad SS has become more of a developer’s toy as opposed to a tool.

Thanks,

Eric L Hackett
Kinder*Morgan CO2
eric_hackett@kindermorgan.com
Ofc: 970.882.5510
Cell: 970.739.9333

WARNING: This record contains Sensitive Security Information that is controlled under 49 CFR parts 15 and 1520. No part of this record may be disclosed to persons without a “need to know”, as defined in 49 CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For U.S. Government agencies, public disclosure is governed by 5 U.S.C. 552 and 49 CFR parts 15 and 1520.

Attachment(s) from Hackett, Eric:

1 of 1 Photo(s) http://groups.yahoo.com/group/toadss/attachments/folder/222097610/item/list
Picture (Device Independent Bitmap) 1.jpg


#2

What does it mean “I’m unable to view tables in the database
explorer”? Do you see empty Tables node? Do you see Database Error message
under Tables node? Can you attach a picture showing it?

Thank you,

Igor.


#3

I think I saw the “Couldn’t open old schema context” right after I
installed the lasted beta. It happened like twice when I was trying to
open the list of tables in a database and this come up in a message box.
I clicked OK or what ever it wanted and the list of tables opened. It
did it one more time I think and now it does not do it.

Hope that is of help.


#4

It means the Tables tab does not get populated. And it is most definitely not a
permissions issue. I can still view them in Toad 4.1 with same credentials.

And I can still view objects in other tabs. Except Agent of course, for every
release since 4.1, which I have mentioned before.

And Matt, it does this EVERY time I open it.

I realize this is a beta program, but I am also a paying customer. Each major
release fails to address the large issues I have, and all the betas continue to
introduce more. I’m near the point of abandoning Toad as a viable option for my
work.

Thanks
Eric L Hackett | 970.882.5510
image005.jpeg


#5

Eric,

This bug was there for only 10 days but unfortunately we post the beta exactly
at the same time. Now it’s fixed. And it was a permission issue. We tried
to use some specific dmv in the query not realizing it’s not accessible
for db_datareader role. It’s still a problem for SQL Azure but we will
resolve it shortly.

Also, I am sure that you’ve already reported the issues you’d had
with Toad but may I ask you to tell us what are the major ones that Toad still
doesn’t address from your point of view?

Thank you,

Igor Manokhin,

Toad for SQL Server Team Lead.
image005.jpeg


#6

The worst is the inability to create and modify jobs in any version later than
4.1. I can view them in the Job Manager, but I can not make any changes to steps
or schedules.

The other one, which is more minor, but still a nuisance, is that code
completion no longer maintains the case of aliases. I’ve written about this and
others have commented on it as well.

I don’t mean to rant, but I was an avid user of Toad for Oracle and I considered
it to be a powerful tool for power users. It just seems like the last few beta
releases of ToadSS have tried to bring in too many new features, with changes to
appearance, icons, placement, rather than firming up the features already in
place, but with maybe a little attention needed.

Thanks
Eric L Hackett | 970.882.5510
image005.jpeg


#7

In regards to point 2 below I don’t understand what exactly the problem is. I
just tried it and it seems to work fine as you can see in this screenshot (I
know the query is bogus, but it hopefully illustrates the point).

Also in regards to the original question about the “Couldn’t open old schema
context”. This is due to me making a small change to how filters are stored and
the error message you see is in regards to Toad not being able to load saved
filters from disc. However you should see it only once per filter and I am
working on the fixing the issue permanently for the future.

/Mauritz
image001.png


#8

In regards to point 2 below I don’t understand what exactly the problem is. I
just tried it and it seems to work fine as you can see in this screenshot (I
know the query is bogus, but it hopefully illustrates the point).

Also in regards to the original question about the “Couldn’t open old schema
context”. This is due to me making a small change to how filters are stored and
the error message you see is in regards to Toad not being able to load saved
filters from disc. However you should see it only once per filter and I am
working on the fixing the issue permanently for the future.

/Mauritz
image005.jpeg


#9

Toad 4.1 Autocomplete maintains the case of the alias as defined, regardless of
how it’s typed before the dot.

Not the case in later versions.

This seems like such a small thing, but to me the whole point of autocomplete is
to keep me from worrying about those small things. And this gets to be
exponentially important the more aliases are present.

As for point 1, I still am unable to view anything in the Tables tab, even with
no filters applied.

This first happened after the find & replace crash I’ve also written about. I’ve
uninstalled and deleted everything realted to 5.0 and re-installed but nothing
has changed.

And I most definitely have permissions to view the objects, so the error message
is misleading.

Thanks
Eric L Hackett | 970.882.5510
Outlook.jpeg


#10

Toad 4.1 Autocomplete maintains the case of the alias as defined, regardless of
how it’s typed before the dot.

Not the case in later versions.

This seems like such a small thing, but to me the whole point of autocomplete is
to keep me from worrying about those small things. And this gets to be
exponentially important the more aliases are present.

As for point 1, I still am unable to view anything in the Tables tab, even with
no filters applied.

This first happened after the find & replace crash I’ve also written about. I’ve
uninstalled and deleted everything realted to 5.0 and re-installed but nothing
has changed.

And I most definitely have permissions to view the objects, so the error message
is misleading.

Thanks
Eric L Hackett | 970.882.5510
Outlook.jpeg


#11

Toad 4.1 Autocomplete maintains the case of the alias as defined, regardless of
how it’s typed before the dot.

Not the case in later versions.

This seems like such a small thing, but to me the whole point of autocomplete is
to keep me from worrying about those small things. And this gets to be
exponentially important the more aliases are present.

As for point 1, I still am unable to view anything in the Tables tab, even with
no filters applied.

This first happened after the find & replace crash I’ve also written about. I’ve
uninstalled and deleted everything realted to 5.0 and re-installed but nothing
has changed.

And I most definitely have permissions to view the objects, so the error message
is misleading.

Thanks
Eric L Hackett | 970.882.5510
image005.jpeg


#12

Toad 4.1 Autocomplete maintains the case of the alias as defined, regardless of
how it’s typed before the dot.

Not the case in later versions.

This seems like such a small thing, but to me the whole point of autocomplete is
to keep me from worrying about those small things. And this gets to be
exponentially important the more aliases are present.

As for point 1, I still am unable to view anything in the Tables tab, even with
no filters applied.

This first happened after the find & replace crash I’ve also written about. I’ve
uninstalled and deleted everything realted to 5.0 and re-installed but nothing
has changed.

And I most definitely have permissions to view the objects, so the error message
is misleading.

Thanks
Eric L Hackett | 970.882.5510
image001.png


#13

Toad 4.1 Autocomplete maintains the case of the alias as defined, regardless of
how it’s typed before the dot.

Not the case in later versions.

This seems like such a small thing, but to me the whole point of autocomplete is
to keep me from worrying about those small things. And this gets to be
exponentially important the more aliases are present.

As for point 1, I still am unable to view anything in the Tables tab, even with
no filters applied.

This first happened after the find & replace crash I’ve also written about. I’ve
uninstalled and deleted everything realted to 5.0 and re-installed but nothing
has changed.

And I most definitely have permissions to view the objects, so the error message
is misleading.

Thanks
Eric L Hackett | 970.882.5510
Outlook.jpeg


#14

Eric,

As I’ve written already, the database error issue is fixed, but we
haven’t posted the beta with the fix yet. To be sure this fix is
addressing your problem, can you please run the following query under the same
credentials and against the same database you ran ToadSS when you got that
database error issue:

select * from sys.dm_db_partition_stats

Please let me know if you can get output from this query without any problem.

Thanks,

Igor.
image001.png


#15

Eric,

As I’ve written already, the database error issue is fixed, but we
haven’t posted the beta with the fix yet. To be sure this fix is
addressing your problem, can you please run the following query under the same
credentials and against the same database you ran ToadSS when you got that
database error issue:

select * from sys.dm_db_partition_stats

Please let me know if you can get output from this query without any problem.

Thanks,

Igor.
Outlook.jpeg


#16

Eric,

As I’ve written already, the database error issue is fixed, but we
haven’t posted the beta with the fix yet. To be sure this fix is
addressing your problem, can you please run the following query under the same
credentials and against the same database you ran ToadSS when you got that
database error issue:

select * from sys.dm_db_partition_stats

Please let me know if you can get output from this query without any problem.

Thanks,

Igor.
Outlook.jpeg


#17

Eric,

As I’ve written already, the database error issue is fixed, but we
haven’t posted the beta with the fix yet. To be sure this fix is
addressing your problem, can you please run the following query under the same
credentials and against the same database you ran ToadSS when you got that
database error issue:

select * from sys.dm_db_partition_stats

Please let me know if you can get output from this query without any problem.

Thanks,

Igor.
image005.jpeg


#18

Eric,

As I’ve written already, the database error issue is fixed, but we
haven’t posted the beta with the fix yet. To be sure this fix is
addressing your problem, can you please run the following query under the same
credentials and against the same database you ran ToadSS when you got that
database error issue:

select * from sys.dm_db_partition_stats

Please let me know if you can get output from this query without any problem.

Thanks,

Igor.
Outlook.jpeg


#19

I get an error message:
SQL Server Database Error: The user does not have permission to perform this
action.

So I’m guessing the method Toad uses for populating the list of tables has
changed.

I am the next-most privileged user on these databases, beneath the full-blown
corporate DBAs. This again raises the question I have asked before. Is Toad
intended as a tool for admin level users only?

Thanks
Eric L Hackett | 970.882.5510
Outlook.jpeg


#20

I get an error message:
SQL Server Database Error: The user does not have permission to perform this
action.

So I’m guessing the method Toad uses for populating the list of tables has
changed.

I am the next-most privileged user on these databases, beneath the full-blown
corporate DBAs. This again raises the question I have asked before. Is Toad
intended as a tool for admin level users only?

Thanks
Eric L Hackett | 970.882.5510
Outlook.jpeg