Select error running sample queries

The sample queries provided as part of ATTOM Cloud are designed to run against the standard (5-county) trial database provided to everyone evaluating ATTOM Cloud and those that have purchased ATTOM Cloud.

Those same queries will only run against the ATTOM CLoud (national) database if have purchased national data for all the datasets used by the query. If you don't have access to one of the tables/views included in the sample query, you will receive a message similar to the following

Expanded Trial

If you have requested an expanded trial, this will be restricted to a subset of geographies and a subset of datasets. This is accomplished by creating a set of custom views that expose the data requested. ATTOM's support team will contact you to advise the names of those custom views. These typically consist of the original table./view with a four-digit number assigned to your company that is then appended to the end (e.g. PropertyFeauture_1234).

Limited Coverage Paid Subscription

If you have purchased ATTOM Cloud data you may have only

Limited geographies such as one or more counties or states;
A limited subset of records such as history for the last 3 years, or mortgage-only records from deeds and mortgages

When a subset of data is purchased we implement this by creating a set of custom views that expose the included data.ATTOM's support team will contact you to advise the names of those custom views. These typically consist of the original table./view with a four-digit number assigned to your company that is then appended to the end (e.g. PropertyFeauture_1234).

Modifying Queries

If you have been provided with customized views, it will be necessary to modify the sample queries to include the custom view names in place of the base table/view. This will usually be in the part of the SQL query containing the FROM and JOIN statements. Having modified the query, you can then save the query as your own custom query.

Note: Your ATTOM Cloud account often includes access to lookup (dimension) tables starting with "Dim" e.g. DimPropertyType. Most of these lookup tables do not need to be customized. You should not have to rename these in your query.

The following code snippet shows three ATTOM cloud tables being used:

FROM
    ADW.PropertyFeature PF
    INNER JOIN ADW.DimCounty DC ON PF.CountyKey = DC.CountyKey
    INNER JOIN ADW.ForeclosureDetail FD ON FD.[ATTOM ID] = PF.[ATTOM ID]

The code is modified to use the names of the custom views assigned

FROM
    ADW.PropertyFeature_1234 PF  -- Property feature tables has been customized
    INNER JOIN ADW.DimCounty DC ON PF.CountyKey = DC.CountyKey  -- DimCounty is not customized
    INNER JOIN ADW.ForeclosureDetail_1234 FD ON FD.[ATTOM ID] = PF.[ATTOM ID] -- ForeclosureDetails table has been customized

It is a good idea to assign aliases to tables/views in this section to minimize the amount of code that needs to be changed to support custom views.