- Posts: 109
ERROR [40001] [Microsoft][ODBC Driver 11 for SQL Server
- JD Cox
- Topic Author
- Offline
- User
Less
More
3 years 11 months ago #3596
by JD Cox
ERROR [40001] [Microsoft][ODBC Driver 11 for SQL Server was created by JD Cox
We’re getting these two errors during data exports. I cannot put my finger on any one thing that’s causing it. I can limit the amount of data and export manually in smaller batches but it still errors from time to time on smaller batches. After some time passes it starts working as planned. I don't think this is a FH issue but we don't see related problems anywhere else. Can you point me in the right direction to figure what’s happening?
Attachments:
Please Log in or Create an account to join the conversation.
- FlowHeater-Team
- Offline
- Admin
3 years 11 months ago #3597
by FlowHeater-Team
Best wishes
Robert Stark
Did this answer your question? We would be grateful if you provide a brief comment as feedback. It may also help others who may have encountered a similar problem.
Replied by FlowHeater-Team on topic ERROR [40001] [Microsoft][ODBC Driver 11 for SQL Server
Hi CD,
DEADLOCKS are occurs in some special cases. I suppose during your MS SQL Server data export the database is used in parallel from ono or more other applications and a lot of transactions for updates are used herewith?
Currently the only way to suppress database DEADLOCKS for such cases is to run your mass data export in a time window with less database activity.
Preview to the next version) with the current Beta “Version 4.2.1.1 Beta2” (see download links below) I´ve implemented a feature that allows you to set the SQL Server “TRANSACTION ISOLATION LEVEL”.
There are two ways to do this.
Beta Version Download
FlowHeater Beta 32 Bit
FlowHeater Beta 64 Bit
FlowHeater Server Beta
MS SQL Server TRANSACTION ISOLATION LEVEL
Prepare Connection SQL Statements
DEADLOCKS are occurs in some special cases. I suppose during your MS SQL Server data export the database is used in parallel from ono or more other applications and a lot of transactions for updates are used herewith?
Currently the only way to suppress database DEADLOCKS for such cases is to run your mass data export in a time window with less database activity.
Preview to the next version) with the current Beta “Version 4.2.1.1 Beta2” (see download links below) I´ve implemented a feature that allows you to set the SQL Server “TRANSACTION ISOLATION LEVEL”.
There are two ways to do this.
- In the
SQL Server Adapter
configuration dialog on “Advanced” tab you can choose the desired “Transaction Isolation Level”, in your case you have to use “READ UNCOMMITTED”.
- In the ODBC Adapter , or all other database Adapters, you can put user defined SQL Statements into the “PrepareConnectionSQL” property. In your case you have to use “SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED”.
Beta Version Download
FlowHeater Beta 32 Bit
FlowHeater Beta 64 Bit
FlowHeater Server Beta
MS SQL Server TRANSACTION ISOLATION LEVEL
Prepare Connection SQL Statements
Best wishes
Robert Stark
Did this answer your question? We would be grateful if you provide a brief comment as feedback. It may also help others who may have encountered a similar problem.
Attachments:
Please Log in or Create an account to join the conversation.
- JD Cox
- Topic Author
- Offline
- User
Less
More
- Posts: 109
3 years 11 months ago #3598
by JD Cox
Replied by JD Cox on topic ERROR [40001] [Microsoft][ODBC Driver 11 for SQL Server
Hey Robert, thanks for the response. Not sure but, we think we may have discovered the problem, an old IP in an active directory referenced on a domain controller no long around. In reference to the Adapters,ODBCAdapter and SqlServerAdapter I’ve been using the ODBC adapter. Other then the obvious connection and the changes you’re working on are there any advantages for one or the other?
As always thanks for your help, JD
As always thanks for your help, JD
Please Log in or Create an account to join the conversation.
Time to create page: 0.283 seconds