Unable to write to MS SQL Server
up vote
0
down vote
favorite
I set up MS SQL Server 2017 Express.
It is fine to use pyodbc to read existing table data.
However, when I created tables, inserted data to tables, the python program finished with no errors.
However, when I refreshed the tables on with MS SQL Management Studio, an error appeared Lock request time out period exceeded as shown below.
When I executed select * from mytable, its status kept on Executing query.
How to solve the problem?
python
sql-server asked Nov 22 at 3:14
Chan
382214
add a comment |
up vote
0
down vote
favorite
I set up MS SQL Server 2017 Express.
It is fine to use pyodbc to read existing table data.
However, when I created tables, inserted data to tables, the python program finished with no errors.
However, when I refreshed the tables on with MS SQL Management Studio, an error appeared Lock request time out period exceeded as shown below.
When I executed select * from mytable, its status kept on Executing query.
How to solve the problem?
python
sql-server asked Nov 22 at 3:14
Chan
382214
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I set up MS SQL Server 2017 Express.
It is fine to use pyodbc to read existing table data.
However, when I created tables, inserted data to tables, the python program finished with no errors.
However, when I refreshed the tables on with MS SQL Management Studio, an error appeared Lock request time out period exceeded as shown below.
When I executed select * from mytable, its status kept on Executing query.
How to solve the problem?
python
sql-server asked Nov 22 at 3:14
Chan
382214
I set up MS SQL Server 2017 Express.
It is fine to use pyodbc to read existing table data.
However, when I created tables, inserted data to tables, the python program finished with no errors.
However, when I refreshed the tables on with MS SQL Management Studio, an error appeared Lock request time out period exceeded as shown below.
When I executed select * from mytable, its status kept on Executing query.
How to solve the problem?
python
sql-server python
sql-server asked Nov 22 at 3:14
Chan
382214
asked Nov 22 at 3:14
Chan
382214
asked Nov 22 at 3:14
Chan
382214
asked Nov 22 at 3:14
Chan
382214
asked Nov 22 at 3:14
Chan
382214
382214
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
This error occurs when a query doesn't get a response from a locked resource. End the session ID which has a lock on the table.
Use the management tools to find the active operations that are stalled and kill them. This should free up the table for future queries.
For future applications, when you begin a transaction make sure there is a matching "commit", this is a really common error when the closing operation results in a prompt that has to be manually closed rather than exiting as expected.
answered Nov 22 at 3:32
Lucas Leodler
534
1
Problem solved. Thank you very much, Lucas.
– Chan
Nov 22 at 7:46
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423354%2funable-to-write-to-ms-sql-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
This error occurs when a query doesn't get a response from a locked resource. End the session ID which has a lock on the table.
Use the management tools to find the active operations that are stalled and kill them. This should free up the table for future queries.
For future applications, when you begin a transaction make sure there is a matching "commit", this is a really common error when the closing operation results in a prompt that has to be manually closed rather than exiting as expected.
answered Nov 22 at 3:32
Lucas Leodler
534
1
Problem solved. Thank you very much, Lucas.
– Chan
Nov 22 at 7:46
add a comment |
up vote
1
down vote
accepted
This error occurs when a query doesn't get a response from a locked resource. End the session ID which has a lock on the table.
Use the management tools to find the active operations that are stalled and kill them. This should free up the table for future queries.
For future applications, when you begin a transaction make sure there is a matching "commit", this is a really common error when the closing operation results in a prompt that has to be manually closed rather than exiting as expected.
answered Nov 22 at 3:32
Lucas Leodler
534
1
Problem solved. Thank you very much, Lucas.
– Chan
Nov 22 at 7:46
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
This error occurs when a query doesn't get a response from a locked resource. End the session ID which has a lock on the table.
Use the management tools to find the active operations that are stalled and kill them. This should free up the table for future queries.
For future applications, when you begin a transaction make sure there is a matching "commit", this is a really common error when the closing operation results in a prompt that has to be manually closed rather than exiting as expected.
answered Nov 22 at 3:32
Lucas Leodler
534
This error occurs when a query doesn't get a response from a locked resource. End the session ID which has a lock on the table.
Use the management tools to find the active operations that are stalled and kill them. This should free up the table for future queries.
For future applications, when you begin a transaction make sure there is a matching "commit", this is a really common error when the closing operation results in a prompt that has to be manually closed rather than exiting as expected.
answered Nov 22 at 3:32
Lucas Leodler
534
answered Nov 22 at 3:32
Lucas Leodler
534
answered Nov 22 at 3:32
Lucas Leodler
534
answered Nov 22 at 3:32
Lucas Leodler
534
534
1
Problem solved. Thank you very much, Lucas.
– Chan
Nov 22 at 7:46
add a comment |
1
Problem solved. Thank you very much, Lucas.
– Chan
Nov 22 at 7:46
1
1
Problem solved. Thank you very much, Lucas.
– Chan
Nov 22 at 7:46
Problem solved. Thank you very much, Lucas.
– Chan
Nov 22 at 7:46
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423354%2funable-to-write-to-ms-sql-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
