Databases Reference
In-Depth Information
From here, we'll delete some rows from the ResellerSales table and
do a bulk insert of these rows to see the behavior of proactive cach-
ing.
3. Open SQL Server Management Studio and execute the following
query to your relational database Adventure Works DW. You will see
3004 rows are retrieved. Select the entire results set and right-click
within the results pane to save the results in a text file. Name the file
AdventureWorksFactResellerSales.CSV.
SELECT * FROM
[dbo].[FactResellerSales]
WHERE OrderDateKey >= '1050' AND OrderDateKey
<= '1280'
4. Execute the following SQL statement to delete the rows from the
table:
DELETE FROM [dbo].[FactResellerSales]
WHERE OrderDateKey >= '1050' AND OrderDateKey
<= '1280'
5. Deploy the Adventure Works project to your Analysis Services in-
stance. Connect to your Analysis Services instance using SQL Serv-
er Management Studio and execute the following MDX query. You
will see the results as shown in
Figure 18-5
.
SELECT [Measures].[Reseller Sales Amount] ON 0,
NON EMPTY [Geography].[Country].MEMBERS ON 1
FROM [Adventure Works]
6. Now you need to set the proactive caching settings for the Reseller-
Sales partition so that changes in source data are automatically de-
tected by Analysis Services and you get real-time data while query-
ing the UDM. Connect to the Analysis Services instance in the Ob-
ject explorer from SSMS. Navigate to the Reseller_Sales_2004 parti-
tion as shown in
Figure 18-5
. Right-click the partition and select
Properties.
Search WWH ::
Custom Search