Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
I'm receiving this error when I try to use a SQL statement to parse the data by date. (Using ODBC connection)
Here's my current SQL Statement:
SELECT fv_v_allocated_time_view_all_modules_lem_filtered.timesheet_fmt_dt, fv_v_allocated_time_view_all_modules_lem_filtered.last_name, fv_v_allocated_time_view_all_modules_lem_filtered.first_name, fv_v_allocated_time_view_all_modules_lem_filtered.skill_type, fv_v_allocated_time_view_all_modules_lem_filtered.rate_1_rate, fv_v_allocated_time_view_all_modules_lem_filtered.project_id, fv_v_allocated_time_view_all_modules_lem_filtered.work_unit_id, fv_v_allocated_time_view_all_modules_lem_filtered.company_code,fv_v_allocated_time_view_all_modules_lem_filtered.employee_or_equipment_id, fv_v_allocated_time_view_all_modules_lem_filtered.equipment_ind, fv_v_allocated_time_view_all_modules_lem_filtered.rate_1_hours, fv_v_allocated_time_view_all_modules_lem_filtered.company_name, fv_v_allocated_time_view_all_modules_lem_filtered.net_billable_time, fv_v_allocated_time_view_all_modules_lem_filtered.last_modified_by, fv_v_allocated_time_view_all_modules_lem_filtered.extra_charges
FROM vdb_track.fv_v_allocated_time_view_all_modules_lem_filtered
WHERE timesheet_fmt_dt > '12/31/2017'
Solved! Go to Solution.
The table or view name was too long, so I tried to give it an alias like below:
SELECT v.timesheet_fmt_dt
FROM vdb_fv_v_allocated_time_view_all_modules_lem_filtered v
WHERE v.timesheet_fmt_dt > '12/31/2017'
This worked for me.
Hi JakeRyan11,
You said when you use SQL, it will cause this problem, if you write "select * from table", will this work ? Or if you don't write sql query, will this work? In addition, I am not sure whether this is caused by sql query or other factors. And whicy type file you are using in ODBC? And you also could check which step will cause error in Edit Queries.
Best Regards,
Zoe Zhi
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
The table or view name was too long, so I tried to give it an alias like below:
SELECT v.timesheet_fmt_dt
FROM vdb_fv_v_allocated_time_view_all_modules_lem_filtered v
WHERE v.timesheet_fmt_dt > '12/31/2017'
This worked for me.
Thanks dax,
The ODBC is connecting to our data lake through Denodo.
I've added "SELECT * FROM TABLE" but now receive this error:
If I do not type in the word "TABLE", then it runs this error:
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
| User | Count |
|---|---|
| 9 | |
| 8 | |
| 8 | |
| 5 | |
| 5 |