According to MS-DOCS about System information schema views, the schema columns definition have a warning note that says:

** Important ** Do not use INFORMATION_SCHEMA views to determine the schema of an object. The only reliable way to find the schema of a object is to query the sys.objects catalog view.

Why can't INFORMATION_SCHEMA views be used to determine the schema of an object?

Is this information erroneous?


1 Answer 1


Yes, the statement there is inaccurate. I talk about this in this blog post (and complained about it in this ancient Connect item), where I implore people to use the sys catalog views over INFORMATION_SCHEMA:

The warning really should state that the INFORMATION_SCHEMA views are incomplete; the wording above implies that they might be incorrect, which in itself is incorrect.

In 2011, they said:

Hi Aaron,
That particular wording has been in the topic since 2005. But, I see your point. We'll revist the wording and try to make it more clear.

Now that we can submit pull requests for suggested changes to the documentation, it might be time for someone to make them pay attention to it again. 13 years is long enough.

  • Perhaps the wording is from the pre-2005 days when we didn't have the schema concept the way we do today? I think, for instance, that INFORMATION_SCHEMA.SCHEMATA returned one row per database in those days. I do agree, it is way overdue to change that wording. The fact that MS can't be bothered is IMO yet another sign that they do not pay much attention (at all) to these views since the birth of the catalog views. Commented Jun 27, 2018 at 11:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.