hi all,
There might be no upgrade path for our ETL investment. So most of us will be doing redesign and a lot of reverse engineering activity for ETL.
Do any one have a bright Idea to model, diagram or document the exisiting ETL investment.
thanks,
joey.
Hi,
I just want to ask, is there a tool that can create a diagram supporting the SSIS package I have created? I would like to know if there is any available tool that can do this task so that I can support my SSIS package documentation.
For example, I have created a Data Flow task that transfer data from a source database to SQL server 2005 destination. I would like to create a diagram that summarizes the task it perform from source to destination automatically. My purpose is that whenever DB users check my SSIS package, they will have a concise idea of how my SSIS package works through my diagram.
If ever you have any ideas about this, please help.
Thanks in advance.
I currently install SQL server 2005 CTP and I couldn't find the diagramming tool which used to view the conceptual model of the database structure, relationships and entities visually. This diagramming tool feature is available in SQL server 2000, however I couldn't find in SQL server 2005. Anyone would like to give me some recommendations or show me where this feature is hidden?
View 1 Replies View RelatedHello,
For management that doesn't have the software I do, I've been using a PDF postscript utility to print the model and give it to them. However, I have to fit the model for the specific page (which is really small, and you have to zoom in), or you have to view it on multiple pages. Well multiple pages can be a pain, because the table you are looking at is on page 1, but the relationships are on page 12, 22, or 50, for example. So I was looking for a tool that is cheap enough to implement that we could look at the entire model on one "surface" (not necessary to print), that the model could be viewed in.
Thanks,
Brian
The Methods & Tools newsletter has released in its archive section thearticle "Database Modelling in UML". This article offers a step by stepapproach to transform a UML object-oriented class model in a purelyrelational database.http://www.methodsandtools.com/archive/archive.php?id=9
View 2 Replies View Relatedi guess really i'm looking for opinions and / or experiences of modelling organisational hierarchies.... anyone?
i'm in the process of creating a logical model (very early stages) of a new datawarehouse. The current OLTP schema stores it as a self referencing key (i.e. parent_group_id). The performance problems involved in aggregating to different levels of the hierarchy causes no end of complaints from customers, as i'm sure you can imagine. So, now we are modelling a datawarehouse for their reporting requirements, i obviously want it to be better
so far i've considered...
1) keeping it as it is
2) allocating a 'node' id and storing the left / right nodes in the hierarchy tree. we've used before when reporting over the OLTP system with report developers building it 'on the fly' as part of their report.
(better explanation than mine... http://www.dbpd.com/vault/9811/kamfn.shtml )
3) an intermediate table storing its 'position' in the hierarchy? not really played with this yet but mr kimball seems to like it
see... http://www.dbmsmag.com/9809d05.html
4) denormalising it completely. i.e. level_1, level_2, level_3, Level4.... for every fact? the advantage of this is that it makes aggregation at any level really easy. the problem is that each of our customers has a different organisation hierarchy, with a different number of levels, and given the OLTP schema there is no limit to the number of levels in a hierarchy
so... thoughts / experiences anyone?
Em
Using SQL 7. I have a table with 2 fields in it that I wish to relateto a lookup table. DDL for table 1:CREATE TABLE [dbo].[tblPedometerReadings] ([ID] [varchar] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,[ReadingDate] [datetime] NULL ,[PedometerReading] [smallint] NULL ,[OtherActivity1] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_ASNULL ,[OtherActivity1Minutes] [smallint] NULL ,[OtherActivity2] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_ASNULL ,[OtherActivity2Minutes] [smallint] NULL) ON [PRIMARY]DDL for table 2:CREATE TABLE [dbo].[tlkpOtherActivities] ([OtherActivity] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_ASNOT NULL ,[EquivalentSteps] [smallint] NOT NULL) ON [PRIMARY]In my database diagram, I want to create a 1-to-many relationshipbetween tblPedometerReadings.OtherActivity1 andtlkpOtherActivities.OtherActivity AND betweentblPedometerReadings.OtherActivity2 andtlkpOtherActivities.OtherActivitiy. I get a long error message whenattempting the relationship between OtherActivity2 and OtherActivity.Is there another schema that would work better?Thanks.
View 3 Replies View RelatedHi Everyone,
I'm attempting to design a schema for a project I working on. The idea is that I can store a list of documents and associate meta data with them.
The problem is that I don't know what that meta data will be at design time. The user will create the meta data fields in the software. For the first design I just had a table called meta field that contained the meta field defintion, and another table called itemdata that contained the document primary key, the metafield primary key and a value encoded as a varchar. This works fine while the list of documents is small.
Another idea I've thought of is to have seperate tables for all of the metafields. This would allow me to be very specific about the values that can be stored in that column etc. It also turns out that for the kind of queries I'm doing its about 4 times as fast. The only problem is that the software will need to create these tables at run time.
What I would like to know is, is this a really bad idea? If so why?. Also are there any other ways I can store this kind of data?
The kind of queries I am doing are find all the documents where metafield 1 is A and metafield 2 is B and metafield 3 is C and metafield 4 is D etc.
Cheers,
Mark
Hi All,Can u please suggest me some books for relational database design ordatabase modelling(Knowledgeable yet simple) i.e. from which we couldlearn database relationships(one to many,many to oneetc.....),building ER diagrams,proper usage of ER diagrams in ourdatabase(Primary key foreign key relations),designing smallmodules,relating tables and everything that relates about databasedesign....Coz I think database design is the crucial part of databaseand we must know the design part very first before starting up withdatabases.....Thanks and very grateful to all of you....Vikas
View 3 Replies View Related