I am using SQL Server 2005 Standard Sp2 I am looking at creating a data warehouse where our OLTP and Archival reports can be run from. I've been tasked by the sponsor to keep latency as low as possible (within an hour if possible). I was
I am promoting a data warehouse to production. Part of the ETL process relies on a stored proc to return data to an SSIS application. This process is causing some issue and I wonder if anyone can shed some light on it. I have a server (A) which has a stored procedure I will call ...
WIn BOL there is a large number of types for the columns of a TIME dimension. The definitions of most are quite clear however some are quite unclear to me. For example What is the differnce between 'Days' and 'DayOfYear', 'Weeks' and 'WeekOfYear'.
If a query is sent to profiler in MDX, the query is shown in the trace log. Thats great. If the query executes without error then it is shown in the trace log. If an error occurs then it is not shown. Although I like to see the MDX when
let's say that I have a table called Order (This is where all the facts of the order stored). and another table call OrderAudit. this is where a select number of orders have been audit.
One of our cubes is set up as monthly snapshots. Our load cycle is only once a month. Every month we have to go open our Excel links to our cubes, and "refresh data" for the new dates to appear. Is there some way that it always refreshes upon opening?