SQL 2005 Any Benefits for Reporting/Creating Cubes ?

• John Burchel

  Hall of Fame

  Points: 3611

  More actions

  July 4, 2006 at 11:56 am

  #115754

  Table A

  Table B

  Table C

  Table D

   

  Cude_1

   

  The currecnt situation is that we have different servers sitting down holding various types of data, we have stored procedures that are scheduled as jobs that update Cube_1, If the jobs does not run, it means that Cube_1 will be out of date because there are a lot of records involved with a lot of IO/CPU resources, we are currently looking for a solution whereby there is a cube table which is automatically updated every time inserts/updates are made on the following tables:

   

  Table A

  Table B

  Table C

  Table D

   

  I am not sure if there is a feature in SQL 2005 which can take care of this problem ?

   

  Or maybe another smarter/sensible way of doing this ?

   

   

   

  ---

  Kindest Regards,

  John Burchel (Trainee Developer)
  

• July 7, 2006 at 8:00 am

  This was removed by the editor as SPAM

• qutub

  SSC Veteran

  Points: 224

  More actions

  August 26, 2008 at 1:40 pm

  #863364

  Try Insert Triggers.......Whenever any data is inserted into any of you A,B,C.... tables....Use triggers to do the respective action tat you wanna perform...........

  Regards

  KB

• Greg Edwards-268690

  SSC-Insane

  Points: 20680

  More actions

  August 27, 2008 at 8:42 am

  #863775

  Sounds like parttioning and incremental updates are something to look at.

  http://msdn.microsoft.com/en-us/library/ms133905.aspx

  You also might want to look at slowly changing dimensions too. How you handle these would also have some impact.

  Greg E