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
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
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
I’ll try one more time J .
By accident, we’d put sys.dm_db_partition_stats into the query that
returned the list of tables. In 10 days I noticed this and we switched back to
sys.partitions. Unfortunately, the latest beta was posted at the same time and
you’d run into this problem. But now it’s gone as you will see in
the next beta. The same problem is still here for SQL Azure databases but again,
it’s not our intention to do so, this problem will be addressed for Azure
as well.
I cannot say you won’t run into any permission problem in ToadSS if you
are connecting with restricted privileges. E.g., member of db_datareader role
only will for sure get some. But at the same time, user with near-admin
privileges shouldn’t have any issues. If it has, then it’s a problem
and we will work to solve it.
Thanks for your comments,
Igor.
I’ll try one more time J .
By accident, we’d put sys.dm_db_partition_stats into the query that
returned the list of tables. In 10 days I noticed this and we switched back to
sys.partitions. Unfortunately, the latest beta was posted at the same time and
you’d run into this problem. But now it’s gone as you will see in
the next beta. The same problem is still here for SQL Azure databases but again,
it’s not our intention to do so, this problem will be addressed for Azure
as well.
I cannot say you won’t run into any permission problem in ToadSS if you
are connecting with restricted privileges. E.g., member of db_datareader role
only will for sure get some. But at the same time, user with near-admin
privileges shouldn’t have any issues. If it has, then it’s a problem
and we will work to solve it.
Thanks for your comments,
Igor.
I’ll try one more time J .
By accident, we’d put sys.dm_db_partition_stats into the query that
returned the list of tables. In 10 days I noticed this and we switched back to
sys.partitions. Unfortunately, the latest beta was posted at the same time and
you’d run into this problem. But now it’s gone as you will see in
the next beta. The same problem is still here for SQL Azure databases but again,
it’s not our intention to do so, this problem will be addressed for Azure
as well.
I cannot say you won’t run into any permission problem in ToadSS if you
are connecting with restricted privileges. E.g., member of db_datareader role
only will for sure get some. But at the same time, user with near-admin
privileges shouldn’t have any issues. If it has, then it’s a problem
and we will work to solve it.
Thanks for your comments,
Igor.
I’ll try one more time J .
By accident, we’d put sys.dm_db_partition_stats into the query that
returned the list of tables. In 10 days I noticed this and we switched back to
sys.partitions. Unfortunately, the latest beta was posted at the same time and
you’d run into this problem. But now it’s gone as you will see in
the next beta. The same problem is still here for SQL Azure databases but again,
it’s not our intention to do so, this problem will be addressed for Azure
as well.
I cannot say you won’t run into any permission problem in ToadSS if you
are connecting with restricted privileges. E.g., member of db_datareader role
only will for sure get some. But at the same time, user with near-admin
privileges shouldn’t have any issues. If it has, then it’s a problem
and we will work to solve it.
Thanks for your comments,
Igor.
I’ll try one more time J .
By accident, we’d put sys.dm_db_partition_stats into the query that
returned the list of tables. In 10 days I noticed this and we switched back to
sys.partitions. Unfortunately, the latest beta was posted at the same time and
you’d run into this problem. But now it’s gone as you will see in
the next beta. The same problem is still here for SQL Azure databases but again,
it’s not our intention to do so, this problem will be addressed for Azure
as well.
I cannot say you won’t run into any permission problem in ToadSS if you
are connecting with restricted privileges. E.g., member of db_datareader role
only will for sure get some. But at the same time, user with near-admin
privileges shouldn’t have any issues. If it has, then it’s a problem
and we will work to solve it.
Thanks for your comments,
Igor.
I apologize if I missed the full meaning of the 'once for each filter'
statement. I see now that if I select my named filters, I get the error for each
one, then it gets removed from the list. After they are all gone, I now see my
objects in the Tables tab. I was also able to create a new named filter
afterward. I never got this far before, because I just kept getting the error,
and didn't know to follow thru and select each filter so it would get removed..
Thanks
Eric L Hackett | 970.882.5510
I apologize if I missed the full meaning of the ‘once for each filter’
statement. I see now that if I select my named filters, I get the error for each
one, then it gets removed from the list. After they are all gone, I now see my
objects in the Tables tab. I was also able to create a new named filter
afterward. I never got this far before, because I just kept getting the error,
and didn’t know to follow thru and select each filter so it would get removed…
Thanks
Eric L Hackett | 970.882.5510
I apologize if I missed the full meaning of the ‘once for each filter’
statement. I see now that if I select my named filters, I get the error for each
one, then it gets removed from the list. After they are all gone, I now see my
objects in the Tables tab. I was also able to create a new named filter
afterward. I never got this far before, because I just kept getting the error,
and didn’t know to follow thru and select each filter so it would get removed…
Thanks
Eric L Hackett | 970.882.5510
I apologize if I missed the full meaning of the 'once for each filter'
statement. I see now that if I select my named filters, I get the error for each
one, then it gets removed from the list. After they are all gone, I now see my
objects in the Tables tab. I was also able to create a new named filter
afterward. I never got this far before, because I just kept getting the error,
and didn't know to follow thru and select each filter so it would get removed..
Thanks
Eric L Hackett | 970.882.5510
I apologize if I missed the full meaning of the ‘once for each filter’
statement. I see now that if I select my named filters, I get the error for each
one, then it gets removed from the list. After they are all gone, I now see my
objects in the Tables tab. I was also able to create a new named filter
afterward. I never got this far before, because I just kept getting the error,
and didn’t know to follow thru and select each filter so it would get removed…
Thanks
Eric L Hackett | 970.882.5510
Thanks again Igor for your patience. I have started the process for getting the
VIEW DATABASE STATE permission for myself and developers. I am glad to see below
that you have taken the steps to make that unnecessary, however, as it can take
time to get these sorts of things approved, as I'm sure you know
Thanks
Eric L Hackett | 970.882.5510
Thanks again Igor for your patience. I have started the process for getting the
VIEW DATABASE STATE permission for myself and developers. I am glad to see below
that you have taken the steps to make that unnecessary, however, as it can take
time to get these sorts of things approved, as I’m sure you know
Thanks
Eric L Hackett | 970.882.5510
Thanks again Igor for your patience. I have started the process for getting the
VIEW DATABASE STATE permission for myself and developers. I am glad to see below
that you have taken the steps to make that unnecessary, however, as it can take
time to get these sorts of things approved, as I’m sure you know
Thanks
Eric L Hackett | 970.882.5510
Thanks again Igor for your patience. I have started the process for getting the
VIEW DATABASE STATE permission for myself and developers. I am glad to see below
that you have taken the steps to make that unnecessary, however, as it can take
time to get these sorts of things approved, as I’m sure you know
Thanks
Eric L Hackett | 970.882.5510
Thanks again Igor for your patience. I have started the process for getting the
VIEW DATABASE STATE permission for myself and developers. I am glad to see below
that you have taken the steps to make that unnecessary, however, as it can take
time to get these sorts of things approved, as I'm sure you know
Thanks
Eric L Hackett | 970.882.5510
Hi Eric,
In regards of issues with jobs:
We are currently addressing some of the issues related to jobs,
can you please let me know directly your environment/user permissions to make sure your problems will be addressed as well. Thanks in advance!
Valentin
Environment is Sql 2005. User permissions are pretty much everything short of
sa, including db_datareader, db_datawriter, create object, create jobm and I am
owner of the jobs I want to modify. I can do everything I need with Toad 4.1.
Does that help?
Thanks
Eric L Hackett | 970.882.5510
