Entitiy relationship diagram for database schema comparator tool

Question

1.00/5 (2 votes)

See more:

Hi,

I want to develop a project for "database schema comparator". I want to draw ERD and DFD diagrams for this project. I am not sure what all entities i should use here. Please help me to understand the entities and tables that we will need.

Regards,

Posted 18-Oct-13 17:56pm

archies_gall

Add a Solution

Comments

[no name] 19-Oct-13 0:06am

What exactly your project will do..?

archies_gall 19-Oct-13 0:30am

Hi,

I will compare two databases on same or different platforms (ie. both databases can be on sqlserver or one can be on sql and other will be on oracle) and will give the difference between them in a window. The differences will be highlighted in red to give more clear picture.

Regards,

[no name] 19-Oct-13 0:59am

Difference between databases..?in what sense..??

archies_gall 19-Oct-13 1:54am

Database will have:
1. Tables
2. Functions
3. Triggers
4. Procedures
5. Views
6. Indexes
7. Synonyms
etc.

Suppose Database1 has 5 table and Database2 has 6 table then the difference should be the 6th table.
If no. of tables in both Databases are same then it will check each table in both databases and will give difference between them like difference in column name or the type(similarly for other objects. it has to check line by line and find the difference. In case of trigger suppose, if there is a difference of semi-colon or comma then that should be highlighted)

Regards,

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)