We don't actually do this yet, but I'm trying to convince our group to do it:

Our project is subordinate to another SOA project that conglomerates data from multiple sources and shares it via web services.

About twice a year, they update (sometimes dramatically) their XML schemas (XSDs).

Since we don't really control the structure of the web service data, it seems to me like a logical design would be to have a SOA master schema where we store information about the web service calls (raw XML requests and responses, timestamps, etc), with a "selector" field that indicates which SQL Server schema contains the "exploded" relational data. Since we don't really control the format of this data, and since it changes dramatically over time, it seems logical to me to use multiple SQL Server schemas as independent namespaces so that the data can reside in its "native" relational format without transformation.

Does this seem like a good design and/or a good use of SQL Server schemas?