No collation was set by the server for the current connection
See original GitHub issueI’m following BulkLoad docs to insert multiple rows at once in my database. I’m getting this error:
No collation was set by the server for the current connection in TediousJS
When my script tries to execute the following line:
bulkLoad.addRow(TYPES.Null, col2, col3, col4, col5, TYPES.Null, col7,
col8, col9, TYPES.Null, TYPES.Null, TYPES.Null);
What does this error mean? Why I haven’t gotten it before using bulkLoad? How do I solve this?
Thanks!
Issue Analytics
- State:
- Created 2 years ago
- Comments:23
Top Results From Across the Web
How to set collation for a connection in SQL Server?
How to set collation for a connection in SQL Server? ; SET COLLATION_ORDER 'French_CI_AS' SELECT · 100 ; SELECT * FROM · WHERE...
Read more >Set or Change the Server Collation - Microsoft Learn
You can set server-level collation via Azure portal or PowerShell and Resource Manager template while you are creating the instance.
Read more >How to fix the collation of a Microsoft SQL Server database
Firstly, create a new database as per the guidelines for your specific application. Ensure the collation is set correctly; as well as any...
Read more >SQL Server collation introduction with collate SQL casting
SQL Server collation indicates set of rules on how information can be stored, compared, and arranged in the T-SQL query statement.
Read more >10.4 Connection Character Sets and Collations
Attempts to use an inappropriate connection character set or collation can produce an error, or cause the server to fall back to its...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Thanks for being so helpful in getting down to the root cause of this issue! I’ll make sure that we really highlight this better in our documentation that the connection is in a half-baked state if you don’t wait for the
.connectcallback to fire. 🙇♂️Okay. 😅 That at least makes sense now! I’m going to try and reproduce this (I have a Azure SQL instance with the same collation settings). I’ll let you know if I can find something!