Stored Procedure executable only after Shrink database
I am using SQL Server 2005 (I know...it is old!) and I wrote a Stored Procedure where the main part make few JOIN
and OUTER APPLY
between tables with 500.000-1.000.000 rows table, then INSERT
the results into a table.
I know that is not clear, but it is very hard for me to explain how the SP works without post the entire code and describe the tables and that would be too long.
The strange fact is that I shrink the database and then EXEC the query it takes 50-60 seconds to be completed while if I din't shrink the DB it never came to the end of the execution either after 2 hours.
I have checked the free space on each disk during the execution and none of them (DATA, LOGS, TemDB, local) have remarkable drop of free space so I would exclude that there are some temporary table that is too big for the disk.
What could I look at to resolve this issue and to understand what is the bottleneck before the shrink?
sql-server sql-server-2005 stored-procedures shrink
New contributor
add a comment |
I am using SQL Server 2005 (I know...it is old!) and I wrote a Stored Procedure where the main part make few JOIN
and OUTER APPLY
between tables with 500.000-1.000.000 rows table, then INSERT
the results into a table.
I know that is not clear, but it is very hard for me to explain how the SP works without post the entire code and describe the tables and that would be too long.
The strange fact is that I shrink the database and then EXEC the query it takes 50-60 seconds to be completed while if I din't shrink the DB it never came to the end of the execution either after 2 hours.
I have checked the free space on each disk during the execution and none of them (DATA, LOGS, TemDB, local) have remarkable drop of free space so I would exclude that there are some temporary table that is too big for the disk.
What could I look at to resolve this issue and to understand what is the bottleneck before the shrink?
sql-server sql-server-2005 stored-procedures shrink
New contributor
add a comment |
I am using SQL Server 2005 (I know...it is old!) and I wrote a Stored Procedure where the main part make few JOIN
and OUTER APPLY
between tables with 500.000-1.000.000 rows table, then INSERT
the results into a table.
I know that is not clear, but it is very hard for me to explain how the SP works without post the entire code and describe the tables and that would be too long.
The strange fact is that I shrink the database and then EXEC the query it takes 50-60 seconds to be completed while if I din't shrink the DB it never came to the end of the execution either after 2 hours.
I have checked the free space on each disk during the execution and none of them (DATA, LOGS, TemDB, local) have remarkable drop of free space so I would exclude that there are some temporary table that is too big for the disk.
What could I look at to resolve this issue and to understand what is the bottleneck before the shrink?
sql-server sql-server-2005 stored-procedures shrink
New contributor
I am using SQL Server 2005 (I know...it is old!) and I wrote a Stored Procedure where the main part make few JOIN
and OUTER APPLY
between tables with 500.000-1.000.000 rows table, then INSERT
the results into a table.
I know that is not clear, but it is very hard for me to explain how the SP works without post the entire code and describe the tables and that would be too long.
The strange fact is that I shrink the database and then EXEC the query it takes 50-60 seconds to be completed while if I din't shrink the DB it never came to the end of the execution either after 2 hours.
I have checked the free space on each disk during the execution and none of them (DATA, LOGS, TemDB, local) have remarkable drop of free space so I would exclude that there are some temporary table that is too big for the disk.
What could I look at to resolve this issue and to understand what is the bottleneck before the shrink?
sql-server sql-server-2005 stored-procedures shrink
sql-server sql-server-2005 stored-procedures shrink
New contributor
New contributor
New contributor
asked 9 mins ago
NicolaesseNicolaesse
1011
1011
New contributor
New contributor
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});
}
});
Nicolaesse is a new contributor. Be nice, and check out our Code of Conduct.
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%2fdba.stackexchange.com%2fquestions%2f227852%2fstored-procedure-executable-only-after-shrink-database%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Nicolaesse is a new contributor. Be nice, and check out our Code of Conduct.
Nicolaesse is a new contributor. Be nice, and check out our Code of Conduct.
Nicolaesse is a new contributor. Be nice, and check out our Code of Conduct.
Nicolaesse is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Database Administrators Stack Exchange!
- 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%2fdba.stackexchange.com%2fquestions%2f227852%2fstored-procedure-executable-only-after-shrink-database%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