http://www.sqlmag.com/authors/author/author/5777463/rsscomment/5777463en-USFri, 25 May 2012 08:39:17 GMTFri, 25 May 2012 08:39:17 GMThttp://www.sqlmag.com/article/data-management/data-warehousing-degenerate-dimensions#commentsAnchorTue, 13 Mar 2012 05:23:02 GMT
Nice explanation]]>vimalraajTue, 13 Mar 2012 05:23:02 GMThttp://www.sqlmag.com/article/data-management/data-warehousing-degenerate-dimensions#commentsAnchorhttp://www.sqlmag.com/article/sql-server-analysis-services/indexing-the-data-warehouse-#commentsAnchorThu, 17 Nov 2011 23:44:32 GMT
Michelle, in your article you say "create a clustered index on the identity column, which you can see in Figure 1." However, Figure 1 shows identity columns with non-clustered indexes. I think you meant to say "create a non-clustered index on the identity column". In general, it makes sense to cluster only on a meaningful business attribute. Since a surrogate key does not have a business meaning, it would not be useful to cluster on it. ]]>Tom HaugheyThu, 17 Nov 2011 23:44:32 GMThttp://www.sqlmag.com/article/sql-server-analysis-services/indexing-the-data-warehouse-#commentsAnchorhttp://www.sqlmag.com/article/data-management/data-warehousing-degenerate-dimensions#commentsAnchorWed, 09 Nov 2011 21:28:23 GMT
very helpful! couldn't be explained better..]]>LaikoWed, 09 Nov 2011 21:28:23 GMThttp://www.sqlmag.com/article/data-management/data-warehousing-degenerate-dimensions#commentsAnchorhttp://www.sqlmag.com/article/data-management/discover-the-star-schema#commentsAnchorWed, 17 Aug 2011 12:57:42 GMT
The figures used as examples in the text are incorrect and seem to have nothing to do with the article content.]]>cwaters123Wed, 17 Aug 2011 12:57:42 GMThttp://www.sqlmag.com/article/data-management/discover-the-star-schema#commentsAnchorhttp://www.sqlmag.com/article/tsql3/sql-by-design-supertypes-and-subtypes#commentsAnchorThu, 07 Jul 2011 14:48:41 GMT
I agree with Kurt. Five years later, this is still a problem. Who to accomodate a database structure that needs to change and the applications developement? This topic has to be treated as one, so if you have a database, surely you should have at least one application accessing it. This has to be done in a way that makes the management of the entities easier. I use to think in databases entities and relationships as part of the application, if it changes, surely the application will have to change. Take Care!]]>MarcosGalvaniThu, 07 Jul 2011 14:48:41 GMThttp://www.sqlmag.com/article/tsql3/sql-by-design-supertypes-and-subtypes#commentsAnchorhttp://www.sqlmag.com/article/sql-server/data-modeling-software-comparison-review#commentsAnchorThu, 19 May 2011 16:17:41 GMT
"I failed to figure out how to generate SQL code." (re: ERwin DM) Really? I don’t think that’s a strength in a reviewer’s repertoire. What happened when you clicked on the very first menu option of "Forward Engineer". And you’ll notice under that your "missing" Check Model feature. Several other "missing features" mentioned in other tools are indeed in those tools, perhaps under different names. I imagine that there was an expectation that these professional, enterprise-class tools should be easy to use for anyone. But architecture tools aren’t just drawing tools. They do require a mastery of terms and features that are common to most of the tools reviewed here. It’s a shame that the reviewer did not have time to reach out to technical support or the many valuable user communities and forums to get peer help on these very basic data modeling tool features so that readers could get a more valid picture of the state of data modeling tools available today. The data management community is really helpful when it comes to supporting other users, even new users of tools. Heck, even the vendors of these tools want users to be successful. Find us - we all want you to love your data. ]]>karenlopezThu, 19 May 2011 16:17:41 GMThttp://www.sqlmag.com/article/sql-server/data-modeling-software-comparison-review#commentsAnchorhttp://www.sqlmag.com/article/sql-server/data-modeling-software-comparison-review#commentsAnchorThu, 19 May 2011 16:16:53 GMT
"I failed to figure out how to generate SQL code." (re: ERwin DM) Really? I don’t think that’s a strength in a reviewer’s repertoire. What happened when you clicked on the very first menu option of "Forward Engineer". And you’ll notice under that your "missing" Check Model feature. Several other "missing features" mentioned in other tools are indeed in those tools, perhaps under different names. I imagine that there was an expectation that these professional, enterprise-class tools should be easy to use for anyone. But architecture tools aren’t just drawing tools. They do require a mastery of terms and features that are common to most of the tools reviewed here. It’s a shame that the reviewer did not have time to reach out to technical support or the many valuable user communities and forums to get peer help on these very basic data modeling tool features so that readers could get a more valid picture of the state of data modeling tools available today. The data management community is really helpful when it comes to supporting other users, even new users of tools. Heck, even the vendors of these tools want users to be succesful. Find us - we all want you to love your data. ]]>karenlopezThu, 19 May 2011 16:16:53 GMThttp://www.sqlmag.com/article/sql-server/data-modeling-software-comparison-review#commentsAnchorhttp://www.sqlmag.com/article/database-administration/database-design-essentials-129493#commentsAnchorMon, 04 Apr 2011 15:02:16 GMT
Looks like the links and InstantDocs are working now. Yeah!]]>bustellMon, 04 Apr 2011 15:02:16 GMThttp://www.sqlmag.com/article/database-administration/database-design-essentials-129493#commentsAnchorhttp://www.sqlmag.com/article/database-administration/database-design-essentials-129493#commentsAnchorMon, 04 Apr 2011 07:44:34 GMT
None of the InstantDoc IDs in the magazine work and none of the links at the end of the electronic version work. :-(]]>bustellMon, 04 Apr 2011 07:44:34 GMThttp://www.sqlmag.com/article/database-administration/database-design-essentials-129493#commentsAnchorhttp://www.sqlmag.com/article/sql-server/data-modeling-software-comparison-review#commentsAnchorFri, 11 Mar 2011 14:15:17 GMT
Thank you so much for letting us know that about the missing link to Table 1. We’ve updated the article, and you should now be able to access Table 1.

Thanks again!

Megan Keller
SQL Server Content Manager
mkeller@sqlmag.com]]>KellerFri, 11 Mar 2011 14:15:17 GMThttp://www.sqlmag.com/article/sql-server/data-modeling-software-comparison-review#commentsAnchorhttp://www.sqlmag.com/article/sql-server/data-modeling-software-comparison-review#commentsAnchorTue, 01 Mar 2011 12:16:44 GMT
Same here, I don’t seem to see any link to table 1--even though I’m logged in and everything.
]]>sgourleyTue, 01 Mar 2011 12:16:44 GMThttp://www.sqlmag.com/article/sql-server/data-modeling-software-comparison-review#commentsAnchorhttp://www.sqlmag.com/article/sql-server/data-modeling-software-comparison-review#commentsAnchorTue, 15 Feb 2011 11:01:16 GMT
Excellent article! Enjoyed reading this very much and have been testing out the trial version of Toad Data Modeler. Definitely glad we don’t have to pay ~$7k to get what we need.]]>HermanTue, 15 Feb 2011 11:01:16 GMThttp://www.sqlmag.com/article/sql-server/data-modeling-software-comparison-review#commentsAnchorhttp://www.sqlmag.com/article/sql-server/data-modeling-software-comparison-review#commentsAnchorFri, 14 Jan 2011 11:09:20 GMT
It looks very help full article. The only, I cannot find Table 1 chart. I tried as it states:

Table 1 contains an excerpt from that chart. You can see the chart in its entirety by going to www.sqlmag.com, entering 128921 in the InstantDoc ID text box, clicking Go, then clicking the Table 1 link.

But it was opening the same page and I can not found Table 1 link.]]>PrakashFri, 14 Jan 2011 11:09:20 GMThttp://www.sqlmag.com/article/sql-server/data-modeling-software-comparison-review#commentsAnchorhttp://www.sqlmag.com/article/sql-server/what-s-the-difference-between-a-data-architect-and-an-enterprise-architect-#commentsAnchorFri, 07 Jan 2011 11:02:36 GMT
Short but clear enough.
Thanks]]>Raymond.AFri, 07 Jan 2011 11:02:36 GMThttp://www.sqlmag.com/article/sql-server/what-s-the-difference-between-a-data-architect-and-an-enterprise-architect-#commentsAnchorhttp://www.sqlmag.com/article/data-management/seven-steps-for-successful-data-warehouse-projects#commentsAnchorThu, 18 Mar 2010 13:15:38 GMT
The "7D" method seems mostly to be a formalization of common sense. It’s sound advice, but an experienced developer (in data warehousing or otherwise) would likely already be following this process pretty closely.]]>Kevin DavisThu, 18 Mar 2010 13:15:38 GMThttp://www.sqlmag.com/article/data-management/seven-steps-for-successful-data-warehouse-projects#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/modernizing-memberships#commentsAnchorWed, 11 Nov 2009 11:47:17 GMT
As I worked for a telephone company I immediately noticed that you could use a phone entity. This way HHPhone attribute and ResPhone attribute could be better normalized. Take Care!]]>MarcosWed, 11 Nov 2009 11:47:17 GMThttp://www.sqlmag.com/article/data-modeling/modernizing-memberships#commentsAnchorhttp://www.sqlmag.com/article/quering/sql-by-design-the-circular-reference#commentsAnchorMon, 24 Aug 2009 20:30:58 GMT
Very easy to follow and read. Thanks]]>PaolaMon, 24 Aug 2009 20:30:58 GMThttp://www.sqlmag.com/article/quering/sql-by-design-the-circular-reference#commentsAnchorhttp://www.sqlmag.com/article/data-management/lessons-learned-from-poor-data-warehouse-design#commentsAnchorTue, 18 Aug 2009 16:43:32 GMT
When reading this article i disagree about the data-quality. A datawarehouse should capture ’as-is’ data which relates and is auditable to the source. The quality system, in my opinion, is a subsystem which relates back to every record inserted in the DWH. I tend to use the following in practice: - use KPI’s on reports which indicate the quality - statistics about anomaly detection and other things reside in the subsystem and relate back to the DWH data at granular level: you’re able to alert people on quality issues but never block it but correct afterwards instead via the source system In this way DWH and source remain synchronized. I think the way it is described in this article promotes the DWH as a cleaner system which bumps bad data: because people aren’t wired in a natural way to the DWH , using the DWH in such a way is much too ambituous, and a true career killer for the DWH Administrator.]]>JohanTue, 18 Aug 2009 16:43:32 GMThttp://www.sqlmag.com/article/data-management/lessons-learned-from-poor-data-warehouse-design#commentsAnchorhttp://www.sqlmag.com/article/tsql3/performance-tuning-the-data-model-thinner-is-better#commentsAnchorFri, 26 Jun 2009 12:49:56 GMT
good article. Every developer should read it! Take Care!]]>MarcosFri, 26 Jun 2009 12:49:56 GMThttp://www.sqlmag.com/article/tsql3/performance-tuning-the-data-model-thinner-is-better#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/logical-modeling#commentsAnchorFri, 26 Jun 2009 12:03:24 GMT
Thank for the articles. Even an experienced person could get something out of these basic serie of articles. Take Care!]]>MarcosFri, 26 Jun 2009 12:03:24 GMThttp://www.sqlmag.com/article/data-modeling/logical-modeling#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/entity-modeling#commentsAnchorFri, 26 Jun 2009 11:40:04 GMT
another good article.]]>MarcosFri, 26 Jun 2009 11:40:04 GMThttp://www.sqlmag.com/article/data-modeling/entity-modeling#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/process-modeling#commentsAnchorFri, 26 Jun 2009 09:07:25 GMT
Good oveview of the process. Take Care!]]>MarcosFri, 26 Jun 2009 09:07:25 GMThttp://www.sqlmag.com/article/data-modeling/process-modeling#commentsAnchorhttp://www.sqlmag.com/article/performance/sql-by-design-why-you-need-database-normalization#commentsAnchorThu, 25 Jun 2009 13:26:23 GMT
Good article about a basic concept. Please, do rate your articles so we can choose to skip the basic ones. Take Care!]]>MarcosThu, 25 Jun 2009 13:26:23 GMThttp://www.sqlmag.com/article/performance/sql-by-design-why-you-need-database-normalization#commentsAnchorhttp://www.sqlmag.com/article/data-management/null-in-the-data-warehouse#commentsAnchorMon, 15 Jun 2009 13:21:54 GMT
Concise and well presented. Thanks!]]>valenaMon, 15 Jun 2009 13:21:54 GMThttp://www.sqlmag.com/article/data-management/null-in-the-data-warehouse#commentsAnchorhttp://www.sqlmag.com/article/data-management/null-in-the-data-warehouse#commentsAnchorTue, 31 Mar 2009 09:45:12 GMT
A good article, again. Specially because you are dealing with a real situation and not just reading the BOL. Keep writing Michelle!]]>MarcosTue, 31 Mar 2009 09:45:12 GMThttp://www.sqlmag.com/article/data-management/null-in-the-data-warehouse#commentsAnchorhttp://www.sqlmag.com/article/data-management/seven-steps-for-successful-data-warehouse-projects#commentsAnchorTue, 31 Mar 2009 09:25:55 GMT
Where can I find more information about the ’7D Method’? I tried to google it but nothing related came up. Thanks.]]>MarcosTue, 31 Mar 2009 09:25:55 GMThttp://www.sqlmag.com/article/data-management/seven-steps-for-successful-data-warehouse-projects#commentsAnchorhttp://www.sqlmag.com/article/data-management/seven-steps-for-successful-data-warehouse-projects#commentsAnchorTue, 31 Mar 2009 08:57:32 GMT
Very well wrote article. Keep writing Michelle!]]>MarcosTue, 31 Mar 2009 08:57:32 GMThttp://www.sqlmag.com/article/data-management/seven-steps-for-successful-data-warehouse-projects#commentsAnchorhttp://www.sqlmag.com/article/data-management/data-warehousing-horizontally-partitioning-the-fact-table#commentsAnchorTue, 24 Mar 2009 13:01:49 GMT
Nice explanation about the subject. I am sorry about my lack of enthusiasm but this is all in BOL.]]>MarcosTue, 24 Mar 2009 13:01:49 GMThttp://www.sqlmag.com/article/data-management/data-warehousing-horizontally-partitioning-the-fact-table#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/making-history23196#commentsAnchorMon, 23 Mar 2009 08:38:36 GMT
Good explanation about a technique that I use a lot. Remember, not matter how good is your design, your plan or your vision of the future... your database will grow. So be prepared (in advance) to save time in the future. I always move historical records, even for tables that seens not to need it. Keep writting Michelle.]]>MarcosMon, 23 Mar 2009 08:38:36 GMThttp://www.sqlmag.com/article/data-modeling/making-history23196#commentsAnchorhttp://www.sqlmag.com/article/backup-recovery/what-is-a-tail-log-backup-#commentsAnchorFri, 21 Nov 2008 07:42:18 GMT
thanx]]>BinodFri, 21 Nov 2008 07:42:18 GMThttp://www.sqlmag.com/article/backup-recovery/what-is-a-tail-log-backup-#commentsAnchorhttp://www.sqlmag.com/article/odbc/desperately-seeking-samples#commentsAnchorSun, 28 Sep 2008 18:37:04 GMT
Don’t forget these resources for the BI folks: www.learnmicrosoftbi.com Microsoft project real http://www.microsoft.com/sql/solutions/bi/projectreal.mspx]]>JohanSun, 28 Sep 2008 18:37:04 GMThttp://www.sqlmag.com/article/odbc/desperately-seeking-samples#commentsAnchorhttp://www.sqlmag.com/article/data-management/bi-without-the-data-warehouse-part-2#commentsAnchorFri, 26 Sep 2008 15:10:32 GMT
Do you really believe we can have BI without data warehouses? I am sorry I don’t think so. May be we just got used to it, may be it is the truth. But really, I can not think about an intelligent tools that run analytics on transactional data without a data warehouse in the middle. Still though, I really enjoyed the two parts of the article. Waiting for more interesting articles. Thank You]]>HaithamFri, 26 Sep 2008 15:10:32 GMThttp://www.sqlmag.com/article/data-management/bi-without-the-data-warehouse-part-2#commentsAnchorhttp://www.sqlmag.com/article/data-management/data-warehouse-workloads-and-use-cases#commentsAnchorFri, 19 Sep 2008 14:20:07 GMT
Nice article. Keep writing Michelle Take Care.]]>MarcosFri, 19 Sep 2008 14:20:07 GMThttp://www.sqlmag.com/article/data-management/data-warehouse-workloads-and-use-cases#commentsAnchorhttp://www.sqlmag.com/article/data-management/bi-without-the-data-warehouse#commentsAnchorSat, 13 Sep 2008 12:23:26 GMT
While anyone who has implemented an enterprise-class data warehouse would agree with your statements about data warehouse justification and efficient delivery there are many good reasons why enterprises continue to pursue data warehousing for their decision support needs. For SMBs, I believe a non-DW approach is a better candidate. Why? Enterprise OLTP systems are usually allready pegged on hardware consumption Enterprise OLTP systems entail more complex business logic which usually has a net result of more ’dirty data’ or atleast the perception of such Regardless of the business size, it can be quite challenging to perform cross business process analysis via muliple source OLTP systems. For all but the smallest companies and budgets the data warehouse is still king. And the failure rate of data warehousing projects is somewhat attributable to the lack of true DW architects available to match business requirements to design and technology implementations.]]>DerekSat, 13 Sep 2008 12:23:26 GMThttp://www.sqlmag.com/article/data-management/bi-without-the-data-warehouse#commentsAnchorhttp://www.sqlmag.com/article/odbc/desperately-seeking-samples#commentsAnchorTue, 02 Sep 2008 07:01:23 GMT
Hi, Another very nice article from Michelle. Thanks for your guidance, I didn’t know Codeplex and now it is alread in my favorites list. keep writing Michelle.... Thanks, Marcos Galvani]]>MarcosTue, 02 Sep 2008 07:01:23 GMThttp://www.sqlmag.com/article/odbc/desperately-seeking-samples#commentsAnchorhttp://www.sqlmag.com/article/data-management/data-warehousing-measuring-the-facts#commentsAnchorTue, 26 Aug 2008 09:22:40 GMT
Very elucidative article, specially for a beginner like me. I will surely read the rest of the articles. Keep Writing Michelle. Marcos Galvani]]>MarcosTue, 26 Aug 2008 09:22:40 GMThttp://www.sqlmag.com/article/data-management/data-warehousing-measuring-the-facts#commentsAnchorhttp://www.sqlmag.com/article/data-management/discover-the-star-schema#commentsAnchorTue, 26 Aug 2008 09:08:50 GMT
I agree with Bala. The articles are great but the website could use some user-friend techniques. Keep writing Michelle. Marcos Galvani]]>MarcosTue, 26 Aug 2008 09:08:50 GMThttp://www.sqlmag.com/article/data-management/discover-the-star-schema#commentsAnchorhttp://www.sqlmag.com/article/data-management/data-warehousing-rapidly-changing-monster-dimensions#commentsAnchorMon, 25 Aug 2008 17:06:38 GMT
Hi, In figure 2 how would you get data from the cube as of a particular date. Example 1: I want to know the current count of customer from the fact table which should be 8 but its going to return 20 since there are 20 records. Example 2: Number of customer as of 2007 which only returns 4 since only 4 records were added to the fact table in 2007 as those were the only customer who had updates. Thanks.]]>VamsiMon, 25 Aug 2008 17:06:38 GMThttp://www.sqlmag.com/article/data-management/data-warehousing-rapidly-changing-monster-dimensions#commentsAnchorhttp://www.sqlmag.com/article/sql-server-analysis-services/indexing-the-data-warehouse-#commentsAnchorWed, 06 Aug 2008 14:23:07 GMT
Wonderful article. Keep writting Michelle.]]>MarcosWed, 06 Aug 2008 14:23:07 GMThttp://www.sqlmag.com/article/sql-server-analysis-services/indexing-the-data-warehouse-#commentsAnchorhttp://www.sqlmag.com/article/backup-recovery/what-is-a-tail-log-backup-#commentsAnchorMon, 14 Jul 2008 14:27:48 GMT
Example syntax of a Tail Log Backup would be nice.]]>TimMon, 14 Jul 2008 14:27:48 GMThttp://www.sqlmag.com/article/backup-recovery/what-is-a-tail-log-backup-#commentsAnchorhttp://www.sqlmag.com/article/business-intelligence-development-studio-bids/data-warehousing-dimensional-role-playing#commentsAnchorTue, 24 Jun 2008 19:03:27 GMT
rhilton, thanks for the feedback! What could we have done better, to give you the information you needed?]]>AnneTue, 24 Jun 2008 19:03:27 GMThttp://www.sqlmag.com/article/business-intelligence-development-studio-bids/data-warehousing-dimensional-role-playing#commentsAnchorhttp://www.sqlmag.com/article/business-intelligence-development-studio-bids/data-warehousing-dimensional-role-playing#commentsAnchorTue, 24 Jun 2008 07:48:00 GMT
Just didn’t get what I needed out of this article.]]>RayTue, 24 Jun 2008 07:48:00 GMThttp://www.sqlmag.com/article/business-intelligence-development-studio-bids/data-warehousing-dimensional-role-playing#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/solutions-by-design-data-modeling-2005#commentsAnchorThu, 01 May 2008 13:18:14 GMT
?]]>CHRISThu, 01 May 2008 13:18:14 GMThttp://www.sqlmag.com/article/data-modeling/solutions-by-design-data-modeling-2005#commentsAnchorhttp://www.sqlmag.com/article/data-management/data-warehousing-rapidly-changing-monster-dimensions#commentsAnchorThu, 13 Mar 2008 17:29:25 GMT
Although I have played with the monster dimension you discuss, I have settled on a couple of different approaches instead. If the things that describe the dimension item are finite, like a billing plan that is changeable, I may settle on a wide fact tables containing many dimension keys to describe a fewer number of facts. To me, splitting out descriptors by subject into new dimensions such as "salary", "geo", or "education" makes it easier for analysts to interpret at query time and supports a natural migration into an OLAP environment. Alternately, if it is a major data load, like from a market research firm, I will treat the combination of descriptors as one or more fact-less fact tables and use a conformed dimension to join them to an additive fact at query time. This is not dissimilar from what you propose except that it is going through the dimension rather than behaving as a peer. I even call it Fact.Demographics.]]>VinceThu, 13 Mar 2008 17:29:25 GMThttp://www.sqlmag.com/article/data-management/data-warehousing-rapidly-changing-monster-dimensions#commentsAnchorhttp://www.sqlmag.com/article/data-management/discover-the-star-schema#commentsAnchorFri, 21 Dec 2007 11:54:41 GMT
Dear Bala, Thanks for taking the time to give your feedback. I’ll be passing this on to our sales team... Diana May Sr Technical Editor SQL Server Magazine]]>DianaFri, 21 Dec 2007 11:54:41 GMThttp://www.sqlmag.com/article/data-management/discover-the-star-schema#commentsAnchorhttp://www.sqlmag.com/article/data-management/discover-the-star-schema#commentsAnchorMon, 17 Dec 2007 08:29:44 GMT
All these advertisements are really really annoying. I feel like navigating through a minefield to finish reading an article. Its not like this is a free website or something in order for me to put up with this annoyance. Could you please address this issue. Quite a few of your articles are thorough, professional and informative. I really enjoy reading your magazine articles. Thanks, Bala]]>BALAMon, 17 Dec 2007 08:29:44 GMThttp://www.sqlmag.com/article/data-management/discover-the-star-schema#commentsAnchorhttp://www.sqlmag.com/article/sql-server-2005/indexed-views#commentsAnchorSun, 02 Dec 2007 17:21:11 GMT
Hi Michelle, Could you give me illustration how overlapping condition looks like. Because in my mind, there are customer indexed view (where PersonType is customer) , Employee indexed view (where PersonType is employee) and Trainer index view (where PersonType is trainer), they refer to Person table that has column PersonType is customer or employee or trainer-type. Let say, there is overlapping condition to display either employee or customer that has age below than 30, so I still have to query to both views or directly query to base table. In partitioned table/partitioned view, still I have to query to those objects(table/view). So could you show me the advantage gained from using indexed view instead of partitioned table/view? Thank you. Kasim Wirama]]>KevinSun, 02 Dec 2007 17:21:11 GMThttp://www.sqlmag.com/article/sql-server-2005/indexed-views#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/data-warehousing-dimension-basics#commentsAnchorMon, 12 Nov 2007 08:54:59 GMT
Planbe, My name is Megan Bearly, and I’m an assistant editor for SQL Server Magazine. I passed your question on to the author, Michelle A. Poolet. Michelle responded, "Oops! Good eye--indeed, these column data types should be NVARCHAR, just the way they are in the PRODUCT_CATEGORY and PRODUCT_SUBCATEGORY tables. Effectively, you’re collapsing the three tables into one, so there’s no need for ProdCatKey or ProdSubCatKey in the PRODUCT_WITH_CATEGORY table, but you will need ProdCatCode, ProdCatName, ProdSubCatCode and ProdSubCatName data, and yes, it’ll be NVARCHAR data. Thanks for catching that, thanks for writing, and thanks for reading SQL Server Magazine! Best regards, Michelle" Please feel free to contact me if you have further questions. Megan Bearly Assistant Editor, SQL Server Magazine mbearly@sqlmag.com]]>meganbearly Mon, 12 Nov 2007 08:54:59 GMThttp://www.sqlmag.com/article/data-modeling/data-warehousing-dimension-basics#commentsAnchorhttp://www.sqlmag.com/article/data-management/data-warehousing-measuring-the-facts#commentsAnchorWed, 07 Nov 2007 13:25:40 GMT
great clarity]]>JerryWed, 07 Nov 2007 13:25:40 GMThttp://www.sqlmag.com/article/data-management/data-warehousing-measuring-the-facts#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/data-warehousing-dimension-basics#commentsAnchorFri, 12 Oct 2007 13:31:49 GMT
The link to What’s a BitMap does not work.]]>DanFri, 12 Oct 2007 13:31:49 GMThttp://www.sqlmag.com/article/data-modeling/data-warehousing-dimension-basics#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/data-warehousing-dimension-basics#commentsAnchorSun, 07 Oct 2007 09:50:20 GMT
Good article and relevant to a current project I’m working on. But one thing I found consusing... The PRODUCT_WITH_CATEGORY table shows the following columns as type INT: ProdCatCode, ProdCatName, ProdSubCatCode and ProdSubCatName. In the PRODUCT_CATEGORY and PRODUCT_SUBCATEGORY tables these columns are NVARCHAR. Is this a typo? If not, please explain the use of the INTs. Thank you]]>ROBSun, 07 Oct 2007 09:50:20 GMThttp://www.sqlmag.com/article/data-modeling/data-warehousing-dimension-basics#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/surrogate-key-vs-natural-key#commentsAnchorMon, 09 Jul 2007 07:25:46 GMT
’Almost make no sense to real developer. The whole article explained some thing every developer knows, and not touch real diffrence between Surrogate Key and Natural Key, pros and cons of each,etc. ’ ’Anonymous User- December 03, 2004 ’ Did you (Anonymous User) even read the article or did you just skim over the first paragraph or 2? There’s no way you can consider yourself a ’real developer’ if you read the entire article and still make the statement that you did. Michelle (the articles author) was very clear on what the differences are between the 2 types of keys as well as provide real world examples/descriptions of each. You would of course have to read the whole article to get those details and so if you did not, which I believe is the case, then you should not be criticizing the author in the way you did. It’s also apparent that not all developers ’knows’ this material because of they did there would not be numerous postings on the internet groups/forumns about this issue. Bottom line, if you are going to be critcial then make sure you’ve reveiwed in full what you are criticizing else you will look foolish to others reading your comments.]]>WILLIAMMon, 09 Jul 2007 07:25:46 GMThttp://www.sqlmag.com/article/data-modeling/surrogate-key-vs-natural-key#commentsAnchorhttp://www.sqlmag.com/article/data-management/discover-the-star-schema#commentsAnchorThu, 05 Jul 2007 11:16:23 GMT
Dear Reader, Thanks for the feedback. Hope you’ll find the whole series useful! Please let us know. Your feedback helps us direct our content to your needs. Diana - Technical Editor, SQL Server Magazine]]>DianaThu, 05 Jul 2007 11:16:23 GMThttp://www.sqlmag.com/article/data-management/discover-the-star-schema#commentsAnchorhttp://www.sqlmag.com/article/data-management/discover-the-star-schema#commentsAnchorTue, 03 Jul 2007 10:05:43 GMT
a concise and excellent read!]]>PaulTue, 03 Jul 2007 10:05:43 GMThttp://www.sqlmag.com/article/data-management/discover-the-star-schema#commentsAnchorhttp://www.sqlmag.com/article/data-types/master-data-management#commentsAnchorMon, 02 Apr 2007 14:50:50 GMT
Nicely Done Michelle! The tech columnists I read again and again and learn from are the ones that continually extend concepts from previous articles and tie them together into themes based on new discussions. Keep it up!]]>TheoMon, 02 Apr 2007 14:50:50 GMThttp://www.sqlmag.com/article/data-types/master-data-management#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/data-modeling#commentsAnchorTue, 31 Oct 2006 08:42:54 GMT
This is a good article on data modelling, keep up the good work!]]>RobTue, 31 Oct 2006 08:42:54 GMThttp://www.sqlmag.com/article/data-modeling/data-modeling#commentsAnchorhttp://www.sqlmag.com/article/systems-administrator/sql-by-design-how-to-choose-a-primary-key#commentsAnchorFri, 22 Sep 2006 22:06:31 GMT
In considering Michelle’s opinion in the identity vs. meaningful value debate, I think it’s important to remember that Michelle wrote this in 1999, before SQL Server finally got around to supporting DRI (Declarative Referential Integrity) which allows for automatic Cascading Updates and Deletes. As I understand it, all enforcement of Referential Integrity was left up to the database designer to handle them through triggers. If I had to write a trigger just to enforce the integrity of a foreign key relationship, I’d most likely be picking keys that would not need to change too! My official, bottom-line, opinion of which primary key method to ALWAYS use is, "Use whatever works best in each situation".]]>DANFri, 22 Sep 2006 22:06:31 GMThttp://www.sqlmag.com/article/systems-administrator/sql-by-design-how-to-choose-a-primary-key#commentsAnchorhttp://www.sqlmag.com/article/scalability/designing-for-performance-lookup-tables#commentsAnchorTue, 19 Sep 2006 16:24:56 GMT
Disagree with "hotspot" theory. A small lookup table is most likely to be memory cached. Disagree with Denormalization hype. Its not as if 100% of all datbase tables are fully normalised in practice. There is always some denormalization going on, and it hurts the least in the relatively smaller lookup tables. Disagree that a single lookup table is non-scalable. You are still free to duplicate the set of values for different categories, so changes to one don’t affect each other. Agree with alpha/natural primary keys for lookups. Agree that it causes obfuscation, but thats a minor tradeoff for not having 100’s of 3-row lookup tables which is another maintenance problem. Note that I am talking about lookup tables of small size which store things like form dropdowns , gender etc. Lets say things that have less than 5 options each. I will still keep things like state and country in their own tables.]]>kobusTue, 19 Sep 2006 16:24:56 GMThttp://www.sqlmag.com/article/scalability/designing-for-performance-lookup-tables#commentsAnchorhttp://www.sqlmag.com/article/systems-administrator/sql-by-design-how-to-choose-a-primary-key#commentsAnchorMon, 10 Jul 2006 07:59:23 GMT
"Now, to be accurate, the old customer 9006CODEN010 should be 9006CODIA010. " No, check your baggage tags! As much as one might wish it to be DIA, which how most people refer to the airport facilities, it is still DEN.]]>JennMon, 10 Jul 2006 07:59:23 GMThttp://www.sqlmag.com/article/systems-administrator/sql-by-design-how-to-choose-a-primary-key#commentsAnchorhttp://www.sqlmag.com/article/tsql3/sql-by-design-supertypes-and-subtypes#commentsAnchorMon, 03 Jul 2006 11:40:09 GMT
I’d like to see a bit more on WHEN super/subtypes are not approriate. For instance, in an inventory system, one may say all items are "Inventory" (the supertype) then create a table for every type of product (subtype) -- you can reach this conclusion simply by transposing "inventory" for "people" in this article (more or less). However that design would be a nightmare, as everytime a new product type is added, the database schema would have to be updated, and the application using it would need to be extended. In the example above, what if a new position is added? Say the company grows and needs "Associate Directors"? The application/database need a redesign. Rather than super/subclass, how about a "metadata" approach -- a table of employee (or inventory) "types", and a table of "type characteristics"? Then adding a new employee/product type becomes a matter of adding a row to the types table, and adding relevant characteristics to the characteristics table. The application is writen once to use the types/charateristics structure... I’d like to see an article discussing the two approaches... In these cases,]]>KURTMon, 03 Jul 2006 11:40:09 GMThttp://www.sqlmag.com/article/tsql3/sql-by-design-supertypes-and-subtypes#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/recursive-relationships#commentsAnchorFri, 05 May 2006 05:03:01 GMT
Clear and concise summary of recursive relationships. This article was of tremendous help to me. Thank you.]]>MichaelFri, 05 May 2006 05:03:01 GMThttp://www.sqlmag.com/article/data-modeling/recursive-relationships#commentsAnchorhttp://www.sqlmag.com/article/quering/the-case-of-the-overlapping-subtype#commentsAnchorThu, 27 Apr 2006 08:35:50 GMT
The help given by this article and the articles it referenced are worth the price of a year’s subscription.]]>EmilyThu, 27 Apr 2006 08:35:50 GMThttp://www.sqlmag.com/article/quering/the-case-of-the-overlapping-subtype#commentsAnchorhttp://www.sqlmag.com/article/scalability/designing-for-performance-lookup-tables#commentsAnchorWed, 29 Mar 2006 09:58:37 GMT
Well thought out and explained.]]>PHILIPWed, 29 Mar 2006 09:58:37 GMThttp://www.sqlmag.com/article/scalability/designing-for-performance-lookup-tables#commentsAnchorhttp://www.sqlmag.com/article/scalability/designing-for-performance-lookup-tables#commentsAnchorMon, 20 Mar 2006 09:59:19 GMT
Michelle, this timely article is important for me because I have a colleague touting his old company used the single-reference table approach and is suggesting we do the same. I’d never heard of the single-reference table approach. The point made is that with so many tables and lookup tables, the single-reference table would cut down the clutter. Your point on the "hot spot" is spot-on and I appreciate the comments by Rhys (rmjcsltd,02/20/06) as well. I will arm myself with these pieces of knowledge and test the waters.]]>JeanMon, 20 Mar 2006 09:59:19 GMThttp://www.sqlmag.com/article/scalability/designing-for-performance-lookup-tables#commentsAnchorhttp://www.sqlmag.com/article/performance/when-not-to-normalize-your-database#commentsAnchorTue, 28 Feb 2006 10:52:37 GMT
This is not really an article - a book review perhaps!]]>RADTue, 28 Feb 2006 10:52:37 GMThttp://www.sqlmag.com/article/performance/when-not-to-normalize-your-database#commentsAnchorhttp://www.sqlmag.com/article/scalability/designing-for-performance-lookup-tables#commentsAnchorMon, 20 Feb 2006 09:36:16 GMT
Michelle, I agree completely that individual tables are nearly always the right thing to do, from a data integrity and design clarity point of view. However, I don’t think that the single table approach has to lead to a performance bottleneck. A single table will be cached in RAM more efficiently than multiple very small tables. If the data really is read-only, then it can be put on a read-only filegroup and SQL Server won’t need to use locks when accessing it. Rhys]]>RhysMon, 20 Feb 2006 09:36:16 GMThttp://www.sqlmag.com/article/scalability/designing-for-performance-lookup-tables#commentsAnchorhttp://www.sqlmag.com/article/auditing/7-steps-to-database-change-control#commentsAnchorTue, 31 Jan 2006 08:49:02 GMT
All words in Figure 1 is not readable. The quality of the scanned image is too poor to read.]]>AbelTue, 31 Jan 2006 08:49:02 GMThttp://www.sqlmag.com/article/auditing/7-steps-to-database-change-control#commentsAnchorhttp://www.sqlmag.com/article/auditing/7-steps-to-database-change-control#commentsAnchorFri, 27 Jan 2006 16:29:44 GMT
Online diagrams do not match article.]]>BenFri, 27 Jan 2006 16:29:44 GMThttp://www.sqlmag.com/article/auditing/7-steps-to-database-change-control#commentsAnchorhttp://www.sqlmag.com/article/performance/running-sql-server-on-raid#commentsAnchorWed, 24 Aug 2005 21:54:48 GMT
Is tempdb data storage really sequential like the transaction logs? I didn’t think it was. I always thought pages were allocated just like any user DB. newsgroup post: http://tinyurl.com/b3qoa Cheers, Mike http://sqlnerd.blogspot.com]]>belwar Wed, 24 Aug 2005 21:54:48 GMThttp://www.sqlmag.com/article/performance/running-sql-server-on-raid#commentsAnchorhttp://www.sqlmag.com/article/performance/sql-by-design-why-you-need-database-normalization#commentsAnchorThu, 28 Jul 2005 00:03:07 GMT
nbnm]]>Anonymous User Thu, 28 Jul 2005 00:03:07 GMThttp://www.sqlmag.com/article/performance/sql-by-design-why-you-need-database-normalization#commentsAnchorhttp://www.sqlmag.com/article/performance/sql-by-design-why-you-need-database-normalization#commentsAnchorMon, 25 Jul 2005 05:53:42 GMT
thanks...i can finish my assignment...thanks for the useful info....really....its availablity makes me really interesting in SQL Server....]]>Anonymous User Mon, 25 Jul 2005 05:53:42 GMThttp://www.sqlmag.com/article/performance/sql-by-design-why-you-need-database-normalization#commentsAnchorhttp://www.sqlmag.com/article/performance/sql-by-design-why-you-need-database-normalization#commentsAnchorWed, 04 May 2005 22:56:03 GMT
Very useful information was given. This will help many people in the world. ]]>Anonymous User Wed, 04 May 2005 22:56:03 GMThttp://www.sqlmag.com/article/performance/sql-by-design-why-you-need-database-normalization#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/data-modeling-q-a#commentsAnchorThu, 28 Apr 2005 09:50:38 GMT
SSN’s such with a suffix of a or b are not valid SSN’s. They are used when a wife is drawing off of her husband’s SSN or vice-versa. The pensioneer is given the a and the dependent is given the b, but they each have their own true unique SSN]]>Anonymous User Thu, 28 Apr 2005 09:50:38 GMThttp://www.sqlmag.com/article/data-modeling/data-modeling-q-a#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/case-tool-visio-2000#commentsAnchorThu, 07 Apr 2005 02:06:32 GMT
Trying to follow in your footsteps, using Visio 200 Enterprise Edition to design an SQL server database. Problem is, your article didn’t even touch on the task of having to link shapes in a Visio document, template, or stencil to database records. This is an horrendous and laborious task. Has anybody created a stencil with these links easily able to be created? I am just wanting to model using a standard ERD diagram. It shouldn’t be such a drawn-out process, surely!]]>Anonymous User Thu, 07 Apr 2005 02:06:32 GMThttp://www.sqlmag.com/article/data-modeling/case-tool-visio-2000#commentsAnchorhttp://www.sqlmag.com/article/performance/when-not-to-normalize-your-database#commentsAnchorSat, 02 Apr 2005 13:32:36 GMT
I was expecting much more Thanks]]>Anonymous User Sat, 02 Apr 2005 13:32:36 GMThttp://www.sqlmag.com/article/performance/when-not-to-normalize-your-database#commentsAnchorhttp://www.sqlmag.com/article/tsql3/materialize-your-views#commentsAnchorWed, 16 Mar 2005 15:24:09 GMT
Great article, thank you!]]>Anonymous User Wed, 16 Mar 2005 15:24:09 GMThttp://www.sqlmag.com/article/tsql3/materialize-your-views#commentsAnchorhttp://www.sqlmag.com/article/data-access/sql-by-design-views-and-stored-procedures#commentsAnchorWed, 02 Mar 2005 16:09:39 GMT
if you compare this to access queries it would be more interesting]]>Anonymous User Wed, 02 Mar 2005 16:09:39 GMThttp://www.sqlmag.com/article/data-access/sql-by-design-views-and-stored-procedures#commentsAnchorhttp://www.sqlmag.com/article/auditing/7-steps-to-database-change-control#commentsAnchorTue, 01 Mar 2005 12:17:05 GMT
Where are the diagrams in the online article - similar to the print article?]]>markskinnergeha Tue, 01 Mar 2005 12:17:05 GMThttp://www.sqlmag.com/article/auditing/7-steps-to-database-change-control#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/data-modeling#commentsAnchorThu, 24 Feb 2005 09:17:53 GMT
its pretty good written, i enjoy reading this article Once again, thanks for the great articles – keep up the work! ]]>TCHOUAThu, 24 Feb 2005 09:17:53 GMThttp://www.sqlmag.com/article/data-modeling/data-modeling#commentsAnchorhttp://www.sqlmag.com/article/auditing/7-steps-to-database-change-control#commentsAnchorTue, 22 Feb 2005 12:04:58 GMT
Well, we created a DCR ( Database change request ) form for making any change to the database. It was sent to the DBA team. Team lead assinged it to one of the team members who was then responsible to see all the effected procedures, triggers, functions, tables, views etc. as a result of the change. It was then modified with the help of a version control product called ’Star Team’ and then the modified changes were applied to the particular development server and tested by the developer involved. The DCR form request was then filed along with the rest of the DCR forms. It resulted in the prevention of a number of bugs in the software development and enhancement process. ]]>Anonymous User Tue, 22 Feb 2005 12:04:58 GMThttp://www.sqlmag.com/article/auditing/7-steps-to-database-change-control#commentsAnchorhttp://www.sqlmag.com/article/auditing/7-steps-to-database-change-control#commentsAnchorMon, 21 Feb 2005 09:45:38 GMT
It would be more useful to have teh spreadsheet available to look at. Figure 1 is to small to see.]]>JASONMon, 21 Feb 2005 09:45:38 GMThttp://www.sqlmag.com/article/auditing/7-steps-to-database-change-control#commentsAnchorhttp://www.sqlmag.com/article/tsql3/sql-by-design-supertypes-and-subtypes#commentsAnchorMon, 31 Jan 2005 12:48:55 GMT
The listings are in the zip file download]]>Anonymous User Mon, 31 Jan 2005 12:48:55 GMThttp://www.sqlmag.com/article/tsql3/sql-by-design-supertypes-and-subtypes#commentsAnchorhttp://www.sqlmag.com/article/performance/sql-by-design-the-foreign-key#commentsAnchorTue, 25 Jan 2005 07:32:25 GMT
Denormalizing data to make it more accessible to users is not required. Just create views instead.]]>bubbagumpTue, 25 Jan 2005 07:32:25 GMThttp://www.sqlmag.com/article/performance/sql-by-design-the-foreign-key#commentsAnchorhttp://www.sqlmag.com/article/systems-administrator/sql-by-design-how-to-choose-a-primary-key#commentsAnchorSat, 22 Jan 2005 20:02:55 GMT
"Consider another simple example - names are attached (artificially) to new-born children, usually by the family head and are generally (in most cases) unique within the family." two words - George Foreman (he named all his sons "George")]]>Anonymous User Sat, 22 Jan 2005 20:02:55 GMThttp://www.sqlmag.com/article/systems-administrator/sql-by-design-how-to-choose-a-primary-key#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/data-modeling#commentsAnchorThu, 23 Dec 2004 01:27:38 GMT
f u c kk you]]>Anonymous User Thu, 23 Dec 2004 01:27:38 GMThttp://www.sqlmag.com/article/data-modeling/data-modeling#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/metamodel-for-reservations-system#commentsAnchorMon, 20 Dec 2004 16:02:26 GMT
I was wondering, how would one take into account the total capacity of the restaurant in this system. eg. say the total seating capacity of the restaurant is 50 and on a given day for a given time say 8 pm its reserved full to its capacity. A customer wants to make a reservation for 8.30 pm for 5 people. Would he/she be allowed to do that? How does the system take care of scenarios like this?]]>manjiritMon, 20 Dec 2004 16:02:26 GMThttp://www.sqlmag.com/article/data-modeling/metamodel-for-reservations-system#commentsAnchorhttp://www.sqlmag.com/article/tsql3/the-search-path-less-traveled#commentsAnchorWed, 08 Dec 2004 08:15:09 GMT
Web listing codes need to be fixed.]]>TunWed, 08 Dec 2004 08:15:09 GMThttp://www.sqlmag.com/article/tsql3/the-search-path-less-traveled#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/surrogate-key-vs-natural-key#commentsAnchorFri, 03 Dec 2004 11:32:35 GMT
Almost make no sense to real developer. The whole article explained some thing every developer knows, and not touch real diffrence between Surrogate Key and Natural Key, pros and cons of each,etc. ]]>Anonymous User Fri, 03 Dec 2004 11:32:35 GMThttp://www.sqlmag.com/article/data-modeling/surrogate-key-vs-natural-key#commentsAnchorhttp://www.sqlmag.com/article/installation2/upgrading-from-sql-server-7-0-to-sql-server-2000#commentsAnchorFri, 26 Nov 2004 03:45:09 GMT
Hi guys, next time it would be better to split this article up to 4 tasks: I) SQL 6.5 to 2K a) upgrade, b) moving; II) SQL 7.0 to 2K a) upgrade, b) moving. Plus some own experience would be nice. Cheers!]]>Anonymous User Fri, 26 Nov 2004 03:45:09 GMThttp://www.sqlmag.com/article/installation2/upgrading-from-sql-server-7-0-to-sql-server-2000#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/case-tool-visio-2000#commentsAnchorSun, 07 Nov 2004 02:41:18 GMT
ahmed]]>Anonymous User Sun, 07 Nov 2004 02:41:18 GMThttp://www.sqlmag.com/article/data-modeling/case-tool-visio-2000#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/process-modeling#commentsAnchorMon, 25 Oct 2004 14:35:01 GMT
Why are information systems and projects both special types of work systems? ]]>Anonymous User Mon, 25 Oct 2004 14:35:01 GMThttp://www.sqlmag.com/article/data-modeling/process-modeling#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/modernizing-memberships#commentsAnchorMon, 27 Sep 2004 07:00:41 GMT
Could this article be extended to offer tips/hints/suggestions on transferring the old data in to the new data structure?]]>TWINCITIESMon, 27 Sep 2004 07:00:41 GMThttp://www.sqlmag.com/article/data-modeling/modernizing-memberships#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/a-business-metadata-repository#commentsAnchorMon, 02 Aug 2004 01:04:43 GMT
This article is great for getting the extended property value holders set up in the DB and for populating them. However, how do you address the problem of allowing non developers to access the metadata? Business Analysts need to be able to access the metadata too. Perhaps linking a named range in Excel to a stored proc call or the equivalent in Word to pipe up-to-date metadata into user friendly apps.]]>Peter Ellis Mon, 02 Aug 2004 01:04:43 GMThttp://www.sqlmag.com/article/data-modeling/a-business-metadata-repository#commentsAnchorhttp://www.sqlmag.com/article/sql-server/declarative-referential-integrity-vs-triggers#commentsAnchorTue, 29 Jun 2004 08:01:27 GMT
Great! All the information you need! :)]]>Muriel Tue, 29 Jun 2004 08:01:27 GMThttp://www.sqlmag.com/article/sql-server/declarative-referential-integrity-vs-triggers#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/surrogate-key-vs-natural-key#commentsAnchorSun, 20 Jun 2004 10:33:28 GMT
It was a great help, very descriptive, good examples. Thanks]]>Aslam Pervez Sun, 20 Jun 2004 10:33:28 GMThttp://www.sqlmag.com/article/data-modeling/surrogate-key-vs-natural-key#commentsAnchorhttp://www.sqlmag.com/article/performance/solutions-by-design-adding-a-questionnaire-to-a-design#commentsAnchorTue, 15 Jun 2004 08:44:35 GMT
A good start but far from a final solution. Having a limit on the questions that can be stored is undesirable. Is there an update to this article after implementation?]]>DANIELTue, 15 Jun 2004 08:44:35 GMThttp://www.sqlmag.com/article/performance/solutions-by-design-adding-a-questionnaire-to-a-design#commentsAnchorhttp://www.sqlmag.com/article/quering/sql-by-design-the-circular-reference#commentsAnchorWed, 09 Jun 2004 06:00:21 GMT
This is interesting, I have a table representing phases of construction. My problem is phase A and B need to be completed before phase C, and when C is completed phases D and E can begin. I established a one/many to one/many relationship table, but it’s circular back to the phase table. Recommendation?]]>ROBERTWed, 09 Jun 2004 06:00:21 GMThttp://www.sqlmag.com/article/quering/sql-by-design-the-circular-reference#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/surrogate-key-vs-natural-key#commentsAnchorTue, 01 Jun 2004 12:33:00 GMT
Very well stated. easy to follow and understand the explanations.]]>molly arriaga Tue, 01 Jun 2004 12:33:00 GMThttp://www.sqlmag.com/article/data-modeling/surrogate-key-vs-natural-key#commentsAnchorhttp://www.sqlmag.com/article/tsql3/materialize-your-views#commentsAnchorSun, 30 May 2004 14:36:50 GMT
A timely piece of information for my job as DBA of a data warehouse. I had heard of something called an "indexed view" before, but never a materialised one. I learned something new, with the "WITH SCHEMABINDING" syntax.]]>James Hippolite Sun, 30 May 2004 14:36:50 GMThttp://www.sqlmag.com/article/tsql3/materialize-your-views#commentsAnchorhttp://www.sqlmag.com/article/data-modeling/process-modeling#commentsAnchorWed, 26 May 2004 02:29:52 GMT
how to make data low daigram in database tables?]]>JeetendraWed, 26 May 2004 02:29:52 GMThttp://www.sqlmag.com/article/data-modeling/process-modeling#commentsAnchor