Skip to content

Commit cc229cd

Browse files
author
Marc Cousin
committed
Still more doc corrections
1 parent 77e89f0 commit cc229cd

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ run sqlserver2pgsql.pl from.
6464
If you just want to convert this schema, run:
6565

6666
```
67-
sqlserver2pgsql.pl -f input_sql_dump \
67+
./sqlserver2pgsql.pl -f input_sql_dump \
6868
-b output_before_script\
6969
-a output_after_script\
7070
-u output_unsure_script
@@ -167,12 +167,12 @@ Now you've generated everything. Let's do the import:
167167

168168
```
169169
# Run the before script (creates the tables)
170-
> psql -U mypguser mypgdatabase -f name_of_before_script
170+
psql -U mypguser mypgdatabase -f name_of_before_script
171171
# Run the kettle job:
172-
> cd my_kettle_installation_directory
173-
> ./kitchen.sh -file=full_path_to_kettle_job_dir/migration.kjb -level=detailed
172+
cd my_kettle_installation_directory
173+
./kitchen.sh -file=full_path_to_kettle_job_dir/migration.kjb -level=detailed
174174
# Run the after script (creates the indexes, constraints...)
175-
> psql -U mypguser mypgdatabase -f name_of_after_script
175+
psql -U mypguser mypgdatabase -f name_of_after_script
176176
```
177177

178178
If you want to dig deeper into the kettle job, you can use kettle_report.pl to display the individual table's transfer performance. Then, if needed, you'll be able to modify the Kettle job to optimize it, using Spoon, Kettle's GUI

0 commit comments

Comments
 (0)