Special characters in sqlserver connector

[erekkiiker]

I have a source sqlserver that has tables with spaces in the name
When I run sling conns discover for such table (wrapped in "schema.my table") it finds the object.
However when I do sling run (wrapping the name same way in quotes) I get error.
11:49PM INF execution failed

fatal:
~ SQL Error
mssql: Incorrect syntax near 'Charges'.

Is there a way to replicate objects with such names or is this some known limitation?

[flarco]

Could you share your config?

[erekkiiker]

Discover that works I run using
sling conns discover onprem_sql -p "DM.UK_Export_Auto Misc Charges Vendor Atlas_v6"
And run that fails I tried with
sling run --src-conn onprem_sql --src-stream "DM.UK_Export_Auto Misc Charges Vendor Atlas_v6" --tgt-conn azure_sql --tgt-object egdp.UK_Export_Auto_Misc_Charges_Vendor_Atlas_v6 --mode full-refresh
Tried also without quotes for src-stream but same result.
For the tables without any spaces in names the connections work.

[flarco]

Can you try with single quote and double quotes? Like this:

sling run --src-conn onprem_sql --src-stream '"DM"."UK_Export_Auto Misc Charges Vendor Atlas_v6"' --tgt-conn azure_sql --tgt-object '"egdp"."UK_Export_Auto_Misc_Charges_Vendor_Atlas_v6"' --mode full-refresh

[erekkiiker]

Yes, this worked. Thank you.
How would I describe this table name in replication yaml? Same syntax doesn't seem to work
streams:
'"DM"."UK_Export_Auto Misc Charges Vendor Atlas_v6"':
object: egdp.{stream_table}
mode: full-refresh

[flarco]

can you share your replication yaml?

[erekkiiker]

I copied yaml from you message and I got the same result. And when I compared to my original one it was identical, including all the spaces.
I notices now that when I copied yaml content it lost the indentation.
Replication with yaml works with other tables that don't have any spaces in their name

[erekkiiker]

Tried also json but still the same result

2024-06-30 22:45:06 INF reading from source database
2024-06-30 22:45:06 INF execution failed

2024-06-30 22:45:07 INF ~ could not parse target table name
invalid table name
fatal:
--- proc.go:267 main ---
--- sling_cli.go:442 main ---
--- sling_cli.go:474 cliInit ---
--- cli.go:286 CliProcess ---
~ failure running replication (see docs @ https://docs.slingdata.io/sling-cli)
--- sling_run.go:188 processRun ---

--------------------------- "DM"."UK_Export_Auto Misc Charges Vendor Atlas_v6" ---------------------------
--- task_run.go:99 func1 ---
~ execution failed
--- task_run.go:523 runDbToDb ---
~ Could not ReadFromDB
--- task_run_read.go:50 ReadFromDB ---
~ could not get format map for sql
--- config.go:709 GetFormatMap ---
~ could not parse target table name
--- schemata.go:559 ParseTableName ---
invalid table name

[flarco]

Thanks, there is a bug, will fix.

[flarco]

It's because of the spaces in the stream name, egdp.{stream_table} gets rendered to egdp.uk_export_auto misc charges vendor atlas_v6 which silently errored since it is not a valid table name.

Fixed here: ff7d4d9
Feel free to build the binary from that branch.
For now, you can simply specify the object name for that stream without using {stream_table} ("egdp"."uk_export_auto_misc_charges_vendor_atlas_v6").

[erekkiiker]

Thanks.