RVR-LTMS-606
- 1 Minute to read
- Print
- DarkLight
- PDF
RVR-LTMS-606
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Issue Summary
- The error code
RVR-LTMS-606
for theload_to_azure_sql
data connector indicates that there is an issue with a non-existent schema when attempting to load data into Azure SQL. This is an external error meaning the schema specified in your Rivery pipeline configuration does not exist in the target Azure SQL database.
- The error code
Action Steps:
- Verify Schema Existence:
- Check your Azure SQL database to confirm that the schema you are trying to load data into actually exists. This can be done through a SQL query or by browsing through the SQL Server Management Studio (SSMS) or Azure portal.
SELECT * FROM information_schema.schemata WHERE schema_name = 'YourSchemaName';
- Check your Azure SQL database to confirm that the schema you are trying to load data into actually exists. This can be done through a SQL query or by browsing through the SQL Server Management Studio (SSMS) or Azure portal.
- Correct Configuration:
- Ensure that the schema name is correctly specified in your Rivery pipeline configuration. Minor typographical errors can lead to such issues. Double-check the spelling and case sensitivity.
- Permissions:
- Confirm that the user account used by Rivery has the necessary permissions to access and write to the schema in Azure SQL. Grant
CREATE
,SELECT
, or any other necessary permissions to your schema as needed.GRANT SELECT, INSERT, UPDATE ON SCHEMA::YourSchemaName TO YourUserName;
- Confirm that the user account used by Rivery has the necessary permissions to access and write to the schema in Azure SQL. Grant
- Check Database Connection:
- If the schema appears to not exist and all configurations seem correct, double-check your connection details in Rivery to ensure it's connecting to the correct database instance where the schema should exist.
- Verify Schema Existence:
External References:
If the issue persists or you need further assistance, please open a ticket with Rivery support.
Was this article helpful?