I have discovered the following in Toad for SQL Server Object Explorer.
In MS SSMS, when one expands the MASTER table folder, there is a SYSTEM tables folder.
If I open up (any version of) Toad for SQL Server, there is no such SYSTEM tables folder.
After exhaustive researching, I cannot find any option to enable this folder.
I feel that this is a matter of concern due that these SYSTEM Tables can be accidently dropped.
See attached screenshot showing the differences.
At the same time Toad is displaying the type of those tables as System: True on the Properties RHS tab.
This issue is addressed in this CR.
(It should show System: False).
WORKAROUND:
None
STATUS:
Waiting for fix in a future version of Toad for SQL Server.
Development is not going to change the Object Explorer in Toad for SQL Server due a definition uses to define a SYSTEM table.
Development agreed a couple of years ago not to use any special value of any extended property as a symptom of an object to be a system one. It does not make a sense because user can easily change this property thus moving an object from system state to user state and vice versa.
There is another issue though: spt_* tables in your example return 1 for sys.all_objects.is_ms_shipped and U for sys.all_objects.type. We also decided to treat those tables as user tables because the fact that MS shipped them does not necessarily means they are system. Additionally, by default system tables in 2005+ are available through DAC connection only: Users cannot directly query or update the system tables except through a dedicated administrator connection (DAC) that should be used only under the direction of Microsoft Customer Services.
