@@ -71,11 +71,10 @@ java -jar gudusoft.dlineage.jar /t mssql /f path_to_sql_file
7171```
7272
7373## 3. Analyze data linege from a database
74- Since version 2.2.0, the dlineage tool no longer connect to the database to analyze
75- the data lineage directly. Instead, it accepts a metadata json file which
76- includes all metadata of a database and analyze the data lineage from this json file.
74+ The dlineage tool can connect to the database instance and analyze the metadata to generate the data lineage automatically.
7775
78- ### 3.1 extract metdata from database
76+
77+ ### 3.1 connect and analyze data lineage
7978Please use ` /fromdb ` parameter to export metadta from the database.
8079
8180` /fromdb ` parameter:
@@ -102,14 +101,23 @@ Please use `/fromdb` parameter to export metadta from the database.
102101
103102` /metadataoutput ` specifies the metadata output directory and file name.
104103
105- for example:
104+ for example, connect to an Oracle database and analzye the data lineage.
105+
106+ ```
107+ java -jar data_flow_analyzer.jar /fromdb "-dbVendor dbvoracle -host 127.0.0.1 -port 1521 -db orcl -user scott -pwd tiger"
108+ ```
109+
110+ ### 3.2 Export the meatadata only
111+
112+ You can also export the meatadata from database and analzye the metadata in two steps:
113+
114+ - Only export the metadta
106115```
107116java -jar data_flow_analyzer.jar /fromdb "-dbVendor dbvoracle -host 127.0.0.1 -port 1521 -db orcl -user scott -pwd tiger" /exportonly /metadataoutput metadata.json
108117```
109118
110- ### 3.2 analyze metadata file
119+ - analyze the metadta that generated in the previous step
111120
112- After you get the metadata.json file, just analyze it like a normal sql file with ` /f ` parmeter:
113121```
114122java -jar gudusoft.dlineage.jar /t oracle /f metadata.json
115123```
0 commit comments