http://www.sqlmag.com/authors/author/author/5542313/rsscomment/5542313en-USFri, 25 May 2012 11:14:52 GMTFri, 25 May 2012 11:14:52 GMThttp://www.sqlmag.com/article/dts/incremental-updates-in-olap-cubes#commentsAnchorTue, 09 Aug 2005 12:19:56 GMT
Extreme useful article.]]>GREGTue, 09 Aug 2005 12:19:56 GMThttp://www.sqlmag.com/article/dts/incremental-updates-in-olap-cubes#commentsAnchorhttp://www.sqlmag.com/article/dts/incremental-updates-in-olap-cubes#commentsAnchorMon, 30 May 2005 13:53:53 GMT
The article is excellent. Thank you very much for publishing it.I have implemented this and it works perfect. Marina - I have put getdate() default value for BATCHDATE field and it always updates the filed with the date and time when the cube has been processed for the last time.]]>Anonymous User Mon, 30 May 2005 13:53:53 GMThttp://www.sqlmag.com/article/dts/incremental-updates-in-olap-cubes#commentsAnchorhttp://www.sqlmag.com/article/dts/incremental-updates-in-olap-cubes#commentsAnchorWed, 08 Dec 2004 12:46:15 GMT
Great article. I just didn’t understand at what poing we are updating BATCHDATE field in SALESID table when creating DTS package. Thanks a lot. Marina. mmaziya@partners.org]]>Anonymous User Wed, 08 Dec 2004 12:46:15 GMThttp://www.sqlmag.com/article/dts/incremental-updates-in-olap-cubes#commentsAnchorhttp://www.sqlmag.com/article/quering/creating-horizontally-partitioned-views#commentsAnchorWed, 28 Jul 2004 17:33:59 GMT
I creared partitioned view, i see performance gain for reading data but performance degrades for my inserts.]]>asomar Wed, 28 Jul 2004 17:33:59 GMThttp://www.sqlmag.com/article/quering/creating-horizontally-partitioned-views#commentsAnchorhttp://www.sqlmag.com/article/quering/creating-horizontally-partitioned-views#commentsAnchorSat, 21 Sep 2002 01:04:54 GMT
I created a partitioned view on 12 tables, one for each month. The primary key of each table is (Date, id) and is clustered. I created a check constraint on date for each table. I did some tests to check the execution time of the same query over the table with data of the whole year and the partitioned view created. For my surprise the second was much bigger! Checking the execution plan of the query over the view it makes a index seek for all the tables, including the ones with date out of the between range. Is ir right? How to make sure The view I created is considered partitioned?]]>marceloSat, 21 Sep 2002 01:04:54 GMThttp://www.sqlmag.com/article/quering/creating-horizontally-partitioned-views#commentsAnchorhttp://www.sqlmag.com/article/quering/creating-horizontally-partitioned-views#commentsAnchorMon, 20 Aug 2001 20:49:24 GMT
Hi, My name is Lucy. I’ve read your article about creating horizontally partitioned views (article dated April 2000 in SQL Server magazine). I working with an application which has a similar problem- large table, but user retrieves only small amount of data. Of course performance is horrible. Partition views would be definitely a solution for our intent to improve performance. Your article was really helpful, but it leaves a few questions unanswered. I’ve tried to search for an answer on web, but could not find anything. You would be a real help if you just take a few minutes and answer on two of my questions. 1. What is the maximum number of tables can be used in single horizontally partitioned view? 2. Does horizontally partitioned view technique works with queries where inner join is used for specifying the criteria? Ex: select * from vwJobAnalysis inner join tblPeriod on vwJobAnalysis.per_end_dt =tblPeriod.per_end_dt It seems that SQL Server scans all tables even when only one table has a data that matches the criteria in table tblPeriod. (I’ve created a few tables, all tables are have the same structure and no indexes. Each table has a constraint on field "per_end_dt" equals to specific period). SQL Server scans only one table if a change my syntax to : SELECT * FROM vwJobAnalysis WHERE per_end_dt IN ("08/15/2001") Please let me know if I did something wrong. -Thanks in advance. Lucy Khovyeva.]]>LUCY KHOVYEVA Mon, 20 Aug 2001 20:49:24 GMThttp://www.sqlmag.com/article/quering/creating-horizontally-partitioned-views#commentsAnchorhttp://www.sqlmag.com/article/quering/creating-horizontally-partitioned-views#commentsAnchorWed, 02 May 2001 15:55:20 GMT
Where can i Fined Listing 1 and Listing 2 ??]]>ZeevWed, 02 May 2001 15:55:20 GMThttp://www.sqlmag.com/article/quering/creating-horizontally-partitioned-views#commentsAnchorhttp://www.sqlmag.com/article/dts/incremental-updates-in-olap-cubes#commentsAnchorTue, 23 Jan 2001 14:15:31 GMT
I want to commend the author on the quality of his writing and the usefulness of the article.]]>JohnTue, 23 Jan 2001 14:15:31 GMThttp://www.sqlmag.com/article/dts/incremental-updates-in-olap-cubes#commentsAnchorhttp://www.sqlmag.com/article/quering/creating-horizontally-partitioned-views#commentsAnchorMon, 28 Aug 2000 08:11:06 GMT
Do horizontally partitioned views work with a large number of tables? Say, over 100? I created the view with just 10 tables and defined contraints on the tables and the results were considerably slower than when I was querying an individual table. I need to find out if I am missing something.]]>david freibrun Mon, 28 Aug 2000 08:11:06 GMThttp://www.sqlmag.com/article/quering/creating-horizontally-partitioned-views#commentsAnchor