Data Warehouse Best Practice: Intra-day DW Loads and Reporting?

Not sure If I understood you correctly, but I guess that the two main problems you may be facing are.

Not sure If I understood you correctly, but I guess that the two main problems you may be facing are: data availability: your users may want to query data that you have temporary removed because you're refreshing it (...this depends on your data loading approach). Performance: The reporting may be affected by the data loading processes. If your data is partitioned, I think it would be a nice approach to use a partitioned switch based data load.

You perform the data load on a staging partition that contains the data that you're reloading (while the datawarehouse partition is still available with all the data for the users). Then, once you have finished loading the data in your staging partition, you can immediately switch the partitions between staging and the datawarehouse. This will solve the data availability problem and could help reducing the performance one (if for instance your staging partition is on a different hard-drive than the datawarehouse).

More info on partitioned data load and other data loading techniques here: msdn.microsoft.com/en-us/library/dd42507...).aspx.

Thanks - I will look at this Partition approach. Currently, not facing any issues, but I wanted to know of Best Practices when doing these type of loads - running every hour at the moment. We're not removing any data, but it can be updated or newly inserted.

– amrit Mar 3 at 9:43.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.