News and Information for the Data Integration community

Fall 2007

 

SAP related solutions

Sage Software related solutions

Data migration solutions

Weekly Webinar on xFusion. Register via email to:
info@softlabsco.com

Newsletter Unsubscribe

More Newsletters

Most Recent

July-August 2007

June 2007

May 2007

April 2007

Mar 2007

Feb 2007

Jan 2007

Dec 2006

Nov 2006

Basics of Data Modeling

Proper data modeling helps you plan better for current or future

changes of your data-centric applications. In this article, we examine some fundamental concepts of data modeling.

Announcements

Latest happenings in xFusion and at Software Labs.

Did you know?


From the support desk

 
 

Basics of Data Modeling
Dr. Pradeep Tapadiya

 

Data modeling is the process of mapping real-world information stored in databases to logical representation of that data. Data modeling helps you in many important ways:

  • It helps you understand relations between various logical entities by providing a logical view of the current system

  • It helps you plan better for future changes

  • While designing a new database, proper data modeling helps you optimize performance of your application

In this article, we look at some basic concepts of data modeling.

Views

A data model primarily consists of two views - physical and logical. The physical view shows database tables, views, columns, relation between tables, etc. The logical view shows how different pieces of data (for example, Customers and Orders) are related to each other from a non-technical perspective. It is a logical blueprint of the physical database.

Note that a data model itself is database agnostic (mostly). The same data model, for example, can be used to create a SQLServer database or an Oracle database.

Entities

Entities are the primary objects used in a data model. An entity is a representation of a single type of data. Examples are Customers, Products, Orders, etc.

Although entities and tables may appear to be similar, do not think of entities as tables. In the end, one entity can be physically implemented as one or more tables.

Attributes

An attribute describes an aspect of the entity. An entity usually consists of many attributes. For example, a Customer may have Business Name, Address, etc.

Relationships

At the physical level, a relation describes how a table is related to another table within the same database. At the logical level, relationships describe how different entities are related to each other.

There are three types of logical relationships in a data model: one-to-one, one-to-many, and many-to-many. A one-to-many relationship, for example, indicates that for every instance in the parent entity, there could be 0, 1 or more instances in the child entity.

Hope this gives you a good overview of data modeling. In the next article, I will discuss an important data modeling technique called Normalization.

xFusion Studio v3.3 Released

We are pleased to announce the release of xFusion Studio v3.3. This new version provides data connectivity and transformation improvements. Read the entire article online here.



New Partners

We are happy to announce the addition of DMC Consulting (USA), Exerve Inc. (USA), Extend Technologies (Australia) and D1 Technologies (USA) to our growing list of partners. xFusion Studio will help them to migrate customers to newer business applications and streamline many data management processes.

Year-end Promotions

These great discounts are available through the end of 2007.

25% discount for new customers (xFusion Studio two user licenses)
75% discount on additional user licenses of xFusion Studio and WebDB Server
20% discount on migration services

Free software training with every product purchase!

Did you know you can easily create fixed-width text output using xFusion? Read more

Support Questions:

Dear Support,

What is the syntax to include a carriage return in a field? I would like to use this in the Address2 field in Marketing Documents. I currently have the following code that concatenates the separate address fields together to fit in the Address2 field. After import the lines run into each other making the field not that easy to read.

([CardCode Map.DelAddress1]+" "+[CardCode Map.DelAddress2]+" "+
[CardCode Map.DelAddrCity]+" "+[CardCode Map.DelAddrState]+" "+
ToString([CardCode Map.DelAddrZipCode])) as 'Address2',

I could not recreate this using carriage returns instead of spaces in between. If you have any insight into how this is accomplished I would greatly appreciate it

Thanks

Hi,

ToString(char(13))+ToString(char(10)) adds a carriage return wherever needed. The query in your case would look like:

[CardCodeMap.DelAddress1]+ToString(char(13))+ToString(char(10))+
[CardCodeMap.DelAddress2]+ToString(char(13))+ToString(char(10))+
[CardCodeMap.DelAddrCity]+ToString(char(13))+ToString(char(10))+
[CardCodeMap.ZipCpode]

Now each of the column is seen in new line.

Hope this helps.

Thank you,

Support


Software Labs, Inc. 1225 Pleasant Grove Blvd. #100, Roseville CA 95768, USA
ph: 1-916-773-6272 fax: 916-773-6281 web: http://www.softlabsco.com email: info@softlabsco.com
unsubscribe via email: unsubscribe@softlabsco.com unsubscribe via web: click here